The technology stack I used to build my first mobile app
• 0 views
It's been 6 months since I started that journey and today I decided to share the technology stack that helped me get here.
By using Expo, the process of building and publishing to the stores is pretty straightforward. And finally, there's a huge community behind it, which makes it easy to find answers and reuse packages.
Since this is a project that I'm working solo, I need the ability to evolve fast without spending too much time setting up and maintaining complex software. That's why I went with Firebase.
There are two database options within Firebase, you can either use the Realtime Database or Firestore. I chose Firestore since it's the evolution of thei Realtime Database. You can read more about the difference between them.
There are many great services that help with user authentication such as Auth0, Okta, etc. However, I wanted something that could also be integrated with database access rules. That's why I went with Firebase Authentication.
One important piece of the app is the ability to upload pictures from your phone. The natural solution was to use Firebase Storage which was pretty cheap and easy to set up.
Unfortunately, Firebase doesn't solve all my problems. Full-text search is one of those things that are not covered in their platform.
In order to have this functionality, I decided to use a service called Algolia which is focused on search. Every new entry to Firestore triggers a Cloud Function that updates the Algolia search index and maintains the data in sync.
Speaking of Cloud Functions, there are some ML capabilities behind the scenes which are all triggered after an action is made in the app. For example:
Whenever a photo is uploaded, I use AutoML Vision to detect text from the image and verify explicit content.
Whenever a review is made, I use AutoML Natural Language to classify entities, get the sentiment, and extract other useful metadata.
Whenever a new cheese is added, I use Text-to-Speech to provide the pronunciation based on its country language.
I love web development, but since my focus is to find product-market fit for the mobile app, I have very limited time to spend on this area.
Now my billing is centralized in one place which makes things easier too.
As you can see, I'm using a lot of tools to make the process of building this app easier and more fun.
One important thing to say is that there's no right or wrong. When it comes to tooling, you have to choose what makes sense to you and your team.
I hope this article can help you choose your own stack for your own apps :)