Recently went through this discussion with two friends. For now we are doing PocketBase for a simple, extendable BaaS, Flutter for front-ends.
We are starting to drool looking at Elixir, Phoenix, and LiveView from afar. But the learning curve would slow us down for the next MVP that we need to put out on a schedule.
Following up, a note on infrastructure. We are cheap, so our LAN is Tailscale. One of us provided a Mac mini where we installed Dokku to host containers and development servers. For internal use we've been very happy.
For exposure to others we'd likely deploy an MVP to the cloud in Dokku as well.
For production we plan to use Kubernetes, but that is an artifact of our skill set.
What a timely question! A couple of friends and I have been wrestling with the question, and coming from the enterprise world, have been retooling for producing code over producing production code for the MVP. We currently are looking working with
* Flutter, with FlutterFlow for UI
* Pocketbase for quick, extendable back end code and basic BaaS
* Heavier emphasis on market validation and strategy than technology
We set a goal that the MVP is barely a mock-up. The other understanding we have is that the backend would have to be 100% rebuilt if / when there is traction, but we were able to get to work in one web meeting.
Pretty much a continuation of what I started in late 2022
* I want some certifications, and just finished studying for Microsoft PowerApps. I'm going to scheduled that test, go for an Azure certification, then Kubernetes. Most of that is for personal interest.
* I started learning F# and have a couple of projects I intend to complete. Right now I'm starting with a serverless Identity Sever. Rust continues to beckon from the sidelines though. I might be distracted, or even worse, try to take the middle path and master both at the same time.
* On Saturday mornings I meet with some friends and we have been working towards our own MicroSaaS efforts; in January we enter market validation for various ideas we have. Ideally at least one idea will survive and I'll be working on that in 2023, which should involve a bit of a learning curve.
* Intentional use of a Zettlekasten is bearing fruit, and I've relaunched my blog with the intention of creating writing products as a result. Need to get RSS working first though.
Recently went through this discussion with two friends. For now we are doing PocketBase for a simple, extendable BaaS, Flutter for front-ends.
We are starting to drool looking at Elixir, Phoenix, and LiveView from afar. But the learning curve would slow us down for the next MVP that we need to put out on a schedule.