React Native At AppLit

Our team at AppLit is no stranger to React Native. We love using it to build amazing mobile apps. This post is about our experience working with React Native.

One Codebase For Both Platforms

Mobile apps we made for startups shared ~95% business logic between iOS and Android. Due to language differences, we needed to have separate codebases for our apps - one in Kotlin, for Android, and another in Swift, for iOS. We heavily invested time in architecture patterns for both platforms and best practices.

With React Native, we were able to unify the codebase. We produced much more in less time without sacrificing the user experience - a HUGE win for us as a team. Making sure the code was running as expected was easier. It was easier to write tests. The development process as a whole was much smoother.

Our Output Soared

Unifying the codebase lets us use one language across both apps! 😀

Engineers could fluidly write code for both platforms. They wrote code once and produced two polished apps. Our team spent less time waiting on code to compile. They were able to understand, review code, and test with more confidence. Each individual could now own more work. The team's morale was at an all-time high!

We Were Getting To Market Even Faster

At AppLit, our mission is to get early stage startups to market fast. If there is a way we can empower our team with tools to achieve this mission, we invest in them. To no surprise, React Native lets us release even faster, iterate more efficiently, and scale with confidence. Our organization levelled up as a whole.

Get to market fast with a product you can be confident in.