SkeleKit.iOS 0.1.5

<p align="center"> <img alt="Header Image" src="Assets/banner/banner.webp"> </p>

<h1 align="center"> SkeleKit </h1> <p align="center"> <a href="https://www.nuget.org/packages/SkeleKit.iOS"> <img alt="NuGet Downloads" src="https://img.shields.io/nuget/dt/SkeleKit.iOS?style=for-the-badge&label=Nuget%20Downloads&color=EFAFFA"> </a> </p>

<table> <tr> <td width="99999" align="center">A C# UI framework for native iOS: real UIKit controls, no storyboards or constraints, zero boilerplate.</td> </tr> </table>

<p align="center"> <a href="https://icysnex.github.io/SkeleKit/motivation/why-skelekit"> <img alt="Static Badge" src="https://img.shields.io/badge/Motivation-695473?style=for-the-badge"> </a> <span> ˙ </span> <a href="https://icysnex.github.io/SkeleKit/getting-started/installation/using-template"> <img alt="Static Badge" src="https://img.shields.io/badge/Getting%20Started-695473?style=for-the-badge"> </a> <span> ˙ </span> <a href="https://icysnex.github.io/SkeleKit/guides/foundations/views-and-view-trees"> <img alt="Static Badge" src="https://img.shields.io/badge/Guides-695473?style=for-the-badge"> </a> <span> ˙ </span> <a href="https://icysnex.github.io/SkeleKit/reference"> <img alt="Static Badge" src="https://img.shields.io/badge/API%20Reference-695473?style=for-the-badge"> </a> </p>

<h3 align="center"> About </h3>

SkeleKit is for C# developers who want native-feeling iPhone and iPad apps without leaving the .NET ecosystem or giving up familiar view trees, bindings, commands, and ViewModels.

SkeleKit is not trying to draw a cross-platform imitation of iOS, it is pure UIKit under the hood. You write plain C# view trees while SkeleKit handles the annoying parts like layout, composition and application setup. UIKit still provides the controls, rendering and interaction - and remains available whenever you need the native APIs.

SkeleKit deliberately focuses on iOS and iPadOS at the moment. It builds on the nativ e**.NET for iOS** bindings and does not depend on MAUI. If you need one shared UI across several platforms, a cross-platform framework will probably make more sense.

<h3 align="center"> Getting Started </h3>

# Install the template and create an app:

dotnet new install SkeleKit.Templates
dotnet new skelekit-ios -n MyApp

// A simple MVVM counter view looks like this:

[Page]
public sealed class MainView : ContentView<MainViewModel>
{
    public MainView(MainViewModel viewModel) : base(viewModel)
    {
        Content = new StackPanel
        {
            Spacing = 4,
            VerticalAlignment = VerticalAlignment.Center,

            Children =
            {
                new Label
                {
              	    Text = Bind(vm => vm.Count)
                      .ConvertTo(val => $"Count: + {val}")
                },
                
                new Button
                {
                    Text = "Click me",
                    Command = viewModel.ClickCommand
                }
            }
        };
    }
}

SkeleKit currently requires the .NET 10 iOS workload and targets iOS 18 or later. The Getting Started guide covers setup, project structure, hot reload, and the first app; the guides cover the rest of the framework.

<p align="center"> <img alt="Screenshots Image" src="Assets/gallery/gallery.webp"> </p>

<table> <tr> <td align="center"> <strong>Native UIKit</strong> <br> Controls wrap UIKit types directly. SkeleKit owns composition and layout, never rendering. </td> <td align="center"> <strong>Clean C# syntax</strong> <br> Define view trees with object initializers instead of XAML, view controllers or Auto Layout constraints. </td> <td align="center"> <strong>Full AOT compatible</strong> <br> Bindings avoid reflection, expression trees, and runtime code generation. </td> <td align="center"> <strong>Application services</strong> <br> Navigation, DI, Dynamic Type, safe areas and keyboard avoidance are integrated. </td> </tr> </table>