undefined | Better HN

0 pointsjohnstorey3y ago0 comments

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.

0 comments

1 comments · 1 top-level

johnstoreyOP3y ago

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.

j / k navigate · click thread line to collapse