Yeah, I’d love to get an update to that discussion, too!
I’m going to develop at least one mobile (native) app in the next weeks and am currently fixed on the flutter + elixir stack, out of familarity with the two languages and development environments.
I’d love to have a current / second opinion on LiveView Native, especially in regard of maturity of both native clients for realtime communication and experience sharing apps.
You’re doing a lot of guessing…
It sounds like you went to code too early. i.e. Before you really knew what had to be built.
You’re right that you should scale back on technology at the start. But even more than you are thinking. I’d go back to paper prototyping if I were you, because from the sounds of it, you really don’t understand the market you are building for. (I could be wrong, I am just going by what you wrote there).
I was doing a lot of guessing. Ultimately, I decided to opt for a straightforward Elixir REST API and React Native solution. It works well. I still wish to add an offline ability, but I think I was overestimating its necessity.
I’m experimenting with Electric SQL for real-time updates, and in the future, hopefully, some offline syncability.
The market I’m building for is me, and I wanted to use it when I’m offline (travelling or in the countryside), but having a more generally available solution is good enough for seeing if anyone else wants to use the app.
Considering it’s been 2.5 years, I’ll pass on the paper prototyping haha
