Show HN: Serverpod – The Missing Server for Flutter

1. Creates a Flutter folder for you, similar to what 'Flutter create' does. It's pre-configured to be able to connect to your local Serverpod server.

2. Creates a server folder where you'd write your API's in Dart. Since Flutter is written in Dart too, this opens up the possibility to share code such as domain models.

3. Creates a client folder with auto-generated code. No manual code changes should be done here, that's the magic trick of this project. This project contains the methods that calls your API's, no need to write redundant code anymore in your Flutter project for each API you just made in your server (backend) project.

It comes with more interesting bells and whistles such as using Docker (compose) to bootstrap every service and also leveraging AWS with Redis, Postgres etc which is setup with Terraform. It goes against the Flutter mass where most of the devs are working with Firebase.

So to answer your question, the Flutter app does not need to be served. It can be, as you said yourself, a local running app that (e.g. phone or desktop). However, the server folder is the one needing to be served for obvious reasons (authentication, safe CRUD operations etc).

Our own surveys show, that enterprise users want to host on a platform of their choice. They are not too eager to switch providers and are more unlikely to use your software if it doesn’t run on AWS

Knowing that, if you want to capture enterprise users, you should offer a managed version of your product on AWS or GCP

For me personally, working at Google wasn't my first choice as I ended up there when the startup I worked at before was acquired. I just felt done with the whole Silicon Valley thing and ended up moving back to Sweden. If I'd pick one big company to work for, it would probably be Google.