Get the weekly radar
One short email with the freshest products, every week.
Copy-paste SwiftUI building blocks with no package dependencies, plus AI code generation.
Grounded in available product and source data
Components arrive as plain SwiftUI pasted into Xcode, with no package to add and no version to pin. Twelve categories make up the SwiftUI component library — avatars, banners, buttons, cards, icons, images, labels, onboarding, paywalls, settings, texts and tiles — which covers most of the surface a small app needs before it ships.
Alongside the library sits generation. Upload a design or describe an interface in words and the app returns Swift; a second mode answers SwiftUI questions and explains code already written, which puts it nearer a tutor than a snippet manager. Both run inside an app distributed through the App Store rather than a web dashboard, so the workflow starts on the device rather than in a browser.
Size is the thing the site leaves unstated. No per-category component count is published and there is no changelog, so "dozens of building blocks" is as precise as the claim gets. On-demand components are framed in the FAQ as a conversation to start rather than a service with terms, which suits a solo project but gives a team no delivery expectation to plan around.
Solo developers and small teams shipping SwiftUI apps get the clearest fit, particularly for onboarding and paywall screens that ship as whole layouts instead of single controls. Anyone needing UIKit coverage, cross-platform output, or a versioned dependency they can update centrally will find the copy-paste model works against them — the absence of a package is exactly what keeps it dependency-free, and exactly what stops updates reaching code already pasted.
No. The site states components are copied in as vanilla SwiftUI with no package dependencies, which keeps the project free of version pinning. The trade-off is that later improvements to a component never reach code that has already been pasted in.
Cases with no matching component are where it earns its place, generating Swift from a design upload or a written description. The assistant also explains code already in a project, so it answers questions about existing work rather than only producing new building blocks.
The site does not publish a number. Twelve categories are listed and the library is described as growing, but with no per-category totals and no changelog, current scope has to be judged inside the app rather than from the marketing page.
The FAQ invites people to get in touch about it rather than describing a defined service. No turnaround, scope or cost is stated, so anyone depending on a particular component landing by a date should agree that directly before building around it.
