appkickstarter logoAppKickstarter

Philosophy

The core principles that AppKickstarter is built upon.

Philosophy

Everything Just Works

An excellent development experience so you can save time, headaches, and effort from having to do redundant & unreliable setup. No dependency hell, managing conflicting dependency versions, incompatible libraries, unexpected build errors, weird UI issues, etc. We want a solid foundation that will work for everyone, every time.

Write React (and only React) once, run anywhere

Other React Native boilerplates still require you to dive into the native XCode projects + Swift code, and Android Studio projects + Kotlin code. With AppKickstarter, you have the ability to only write React code (via React Native & Expo) to build your app, while also giving you the flexibility of optionally using native code for additional functionality.

Essentials for an app business, not just development

One problem with other boilerplates is they're extremely focused on the tech stack. They will provide great code linting, unit test frameworks, CI/CD, fancy API frameworks & state management libraries, etc.

While these aspects are important (and we have these features as well), we provide the key aspects of making your app a successful business, with onboarding screens that convert users into customers, monetization to accept payments & in-app purchases, analytics to learn how to maximize revenue from users, in addition to choosing great technologies & libraries.

Low/No Cost

You shouldn't be spending money on tools and infrastructure if you don't have customers yet. It should avoid a flat cost, or have a generous free tier. You should aim to make your project self-sustaining, with the goal of avoiding any recurring costs upfront and finding services that scale with you.

Simple, Familiar, Standard

The whole point of a boilerplate is to minimize the friction to get your app out there, and start earning. We choose simple tools, frameworks, libraries that are industry-standard, developers are familiar with, and have a minimal learning curve.

You should not be spending a ton of time learning 50 fancy, hot, new technologies and frameworks. Instead, you should feel immediately right at home, with solid foundations and the flexibility to swap things out if desired. For example, most developers know TailwindCSS, so we style our components using Nativewind instead of some of the other fancy frameworks with their unique APIs.