SoarStarter

Introducing SoarStarter: One Starter Family, Eight Platforms

Why we built the same full-featured product starter for Next.js, Nuxt, TanStack Start, SwiftUI, Kotlin, Expo, Electron, and Tauri.

SoarStarter Team

Every product starts the same way. Before you write a single line of the thing you actually want to build, you set up authentication, sessions and OAuth callbacks. You wire up payments and webhooks. You build a settings screen, a pricing page, legal pages, transactional emails, error tracking, i18n. Two or three weeks disappear into plumbing that your users will only notice if it's broken.

Then you decide to ship a mobile app too, and you do it all again — with a different auth SDK, a different payment model, and a different set of platform rules.

SoarStarter is our answer to that loop: one product blueprint, implemented natively on eight platforms.

The template family

Every template is a complete, runnable app — not a component library, not a CLI that scaffolds empty folders. You clone it, add your keys, and you have a working product with auth, payments, and settings on day one.

Web

All three web templates share the same backbone: Better Auth for email/password and social login, Drizzle ORM on PostgreSQL, Creem for payments (subscriptions and one-time purchases, with Creem acting as merchant of record so you don't handle global sales tax yourself), transactional email, i18n, a blog, documentation pages, and AI endpoints built on the AI SDK.

Mobile

  • SwiftUI — native iOS, Swift end to end.
  • Kotlin — native Android with Jetpack Compose, Material 3, and Hilt.
  • Expo — React Native for iOS and Android from one codebase, with Expo Router and EAS.

The mobile templates share Supabase for auth and backend (including Sign in with Apple and Google), RevenueCat for in-app subscriptions and paywalls, Sentry for crash reporting, push notifications, onboarding flows, and settings screens.

Desktop

  • Electron — Chromium-based, maximum rendering consistency, built with React and Vite.
  • Tauri — Tauri 2 with a Rust core and the OS webview, for small and fast binaries.

Both desktop templates ship Supabase auth with deep-link OAuth callbacks, auto-updates, system tray integration, notifications, and window-state persistence.

The philosophy: same blueprint, native idioms

The eight templates implement the same product: authentication, subscription billing, a paywall or pricing page, user settings, and the supporting pages every real product needs. But each one is written the way its platform community would write it.

The SwiftUI template doesn't try to look like a React app in Swift — it uses Swift concurrency and native navigation. The Kotlin template uses Hilt and Compose idioms. The Nuxt template uses composables and Nitro server routes, not a port of React patterns. If you hire a developer who knows the platform, the codebase should feel familiar to them immediately.

This also means the templates are honest about platform differences. Payments are a good example: the web and desktop templates use Creem, because on those platforms you control the payment flow. The mobile templates use RevenueCat, because on iOS and Android the app stores control it. Same product feature, correct implementation for each platform.

Documentation that matches the code

Each template has its own documentation root covering setup, architecture, auth, payments, deployment, and customization — written against the actual template code, not generic advice. The docs are part of the product: when you're deciding whether a template fits your project, you can read exactly how it works before buying.

Pricing

Templates are one-time purchases with lifetime updates — no subscription for your starter code. Web templates are $49 each; mobile and desktop templates are $29 each. If you're building across platforms (or just want the option), the all-access bundle includes all eight templates for $149.

What's next

We'll use this blog to publish what we learn from maintaining the same product on eight platforms: honest framework comparisons, deep-dives into the stack choices (why Better Auth, why a merchant of record, why RevenueCat), and step-by-step launch guides.

If you're starting a product this month, pick your platform, open the live demos, and skip the plumbing weeks.