What is the technology stack for your mobile app?

shevelopher's profile thumbnail
For Native: Mobile: Kotlin / swift with some Firebase integrationFor Hybrid, we use Flutter with some Firebase integrationBackends: I've worked on recent projects with AWS and google Cloud as well as purely in house solutions. I think a lot of the decision for a backend depends on the type of personal information you'll store there (although cloud solutions have gotten better for security. I think your mobile solution and backend solution decisions can be made almost completely separately for what fits the constraints and needs of each and then you just need to build the right bridge between to the two (whether that's a rest api, graphql, etc). Firebase is a good choice to integrate with all mobile apps because it gives you crashlytics, analytics tracking, authenticated log in, in app chat, storage, ad mob, ML kit, app distribution and more (there are many extensions available) with mobile first integration. It sits on top of google cloud.
SujathaMudupalli's profile thumbnail
Hi @shevelopher thank you very much for your response. I prototyped with flutter+firebase, liked firebase, pretty straightforward to start with. But I decided to go with AWS and exploring different backend like node.js & Laravel. Do you have experience with those? My frontend still will be flutter. Thanks.
annamclaughlin's profile thumbnail
At one startup I was at, we used reactive native on the front end, react for our web app, and then scala for the backend. The backend was written in scala because that's the language the main developer picked early on.At my current company, we're using ruby on rails for the backend, vue for the front end, and react native for the app. I'm also consulting with a company right now that's using firebase and react native for their initial launch.I don't know what kind of app you're building but the benefit of react native is that you get an andoird and iOS app from one codebase.
SujathaMudupalli's profile thumbnail
Hi @annamclaughlin, thanks for the info. I also prefer a cross platform framework, decided to go with flutter. And for the backend, exploring node.js, laravel or django.