Products
Design engineering across web and native.
A shared foundation, ecosystem surfaces built on it, and the native platforms next. Take any one of them on its own.
Web platform
A shared styling foundation, and the ecosystems built on top of it.
Style
ShippingOne foundation, and every web ecosystem stands on it.The shared styling foundation — tokens, utilities, and the visual primitives every Amkit web surface is built on.More@teasim/astro
ShippingEverything that computes, and renders nothing.The content layer — navigation, validation, markdown twins, and the machine-readable routes.MoreReact
In progressInteractive applications, with the hard parts already solved.The Amkit surface for interactive application experiences — elements, hooks, and higher-level widgets.More@teasim/aster
ShippingArrangement, and never a second opinion on a surface.The page-level blocks — a documentation shell, a header run, a footer, a nav tree, a pager.More@teasim/astra
ShippingElements that render markup, not opinions.Accessible elements that render the markup you would have written, and carry their behaviour with them.More
Native platform
Platform surfaces for Apple, Android, HarmonyOS, and the desktop.
Apple
PlannedSwift and SwiftUI, held to the same standard.The planned Amkit surface for Apple platforms — Swift and SwiftUI, with the same design-engineering standards as the web.MoreAndroid
PlannedKotlin and Compose, on the same foundations.The planned Amkit surface for Android — Kotlin and Jetpack Compose, sharing the design-engineering standards of the web surfaces.MoreHarmonyOS
PlannedArkTS and ArkUI, treated as a first-class target.The planned Amkit surface for HarmonyOS — ArkTS and ArkUI, with the same interface standards as every other Amkit platform.MoreDesktop
PlannedGPUI, for interfaces that have to stay fast.The planned Amkit surface for native desktop applications, built on GPUI.More