Blog 20: The tech stack that worked for us
- Idea2Product2Business Team
- Jul 1, 2023
- 2 min read
Updated: Dec 12, 2024
What tech stack should we use? A common confusion especially among non-programming professionals.
For the first product version, we chose a tech stack that served our current needs. We could always upgrade as we gain traction.
However, few pointers we had in mind, during the tech selection process were:
· Flexibility and simplicity of the technology
· Do we have the necessary expertise?
· Is the technology scalable?
· Does it fall under our budget?
· Future potential of this tech?

Based on our requirements and prior tech experience we chose the Flutter stack:
Front-end
Flutter:
Open-source UI software development kit created by Google.
Can develop cross platform applications from a single codebase (i.e., Android, iOS, the web and etc.).
Read more: https://flutter.dev
Back-end
Firebase:
A backend-as-a-Service (BaaS) app development platform. Part of Flutter ecosystem.
Provides hosted backend services such as two cloud-based databases, cloud storage, remote configuration, cloud functions, Firebase extensions, authentication, crash reporting, machine learning, and hosting.
Read more: https://firebase.google.com/products-build
Among the two databases, we chose Cloud Firestore compared to Realtime Database. Cloud Firestore is a JSON-compatible document database. Suitable for apps with data models that require query ability, scalability, and high availability.
Other tools used include:
‘Mailgun’:
Primarily used it to send email validations, to new users, signing up on our app.
Read more: https://www.mailgun.com
‘MailSlurp’:
API platform for building SMS and email applications, automations, and integration tests.
Primarily used it as an end-to-end email testing service.
Read more: https://app.mailslurp.com/login/
Refer to blog 21 for 10 widely used tech-stacks.
Refer to blog 84 for a further list of tools used for product development.
While we chose Flutter stack, we will talk more about different technologies and our other tech experiences in future blogs. Refer blog 63 to learn more on Technical Requirements Document, TRD (tech stack will be the key section).
Jump to blog 100 to refer to the overall product management mind map.
I wish you the best for your journey. 😊