#Flutter for web dev full#
#Flutter for web dev code#
#Flutter for web dev Offline#

Definitely, I’ll try it in the future.įE/mobile dev is hard. Ps: liveview native is very interesting since it is the only cross-platform framework AFAIK that uses the same building blocks that native frameworks use, so it is a better long-term investment knowledge-wise IMO. I also love functional programming, so it is a blessing to have this settled in the level of the language, without arguments. I was really invested in mobile apps but in the end, I chose to go all-in in Elixir since it will give me more possibilities to create different types of apps in a high-level quality. If you go the web route, well, Elixir is my current bet. If you go the mobile route, focus on the client and use a BaaS (in iOS you even have CloudKit “for free”). So my advice to you is, and what I am doing myself: do not try to win on all platforms at once as a solo dev. This is the most important thing a solo dev must have in order to have a chance to compete with a company with more resources IMO.īoth in Swift and Elixir ecosystems I felt that with very few tools I could create really solid applications, that in other ecosystems it would be nearly impossible to accomplish by myself with the same quality, velocity, and scope. The main reason: cohesive and convergent ecosystem. create a web app, I would choose Elixir (with Phoenix and LiveView).Īnd the most important part of the message.create a mobile app, I would create a native iOS app with Swift & SwiftUI.I work as Frontend/JS Developer, so I knew what was available in the frontend web space.Īfter several months of experiments, what I concluded was…Īs a solo developer, creating an indie business, if I want to: On mobile: Flutter, Swift & SwiftUI, Kotlin & Jetpack Compose. I have several app ideas (web & mobile), and started to try different stacks to see “what they taste like”. Well, I will share a short summary of a journey I went through myself since your current conflicts are very related to the ones I had.

#Flutter for web dev code#

With LiveView you might have to touch some backend code again to switch front end to native if (and with mobile, it’s more of a when than an if) needed. You can wrap a web view or move to native and even switch from flutter to compose etc if you have this option. You need to keep your options open and having an API is optimal for that. For MVP you could maybe stick to familiar tech stack and do something like OnsenUI or Ionic, and then move to more native solution when you have some dedicated availability? I haven’t been on this space since 2017 but those were good enough back then.Įdit: I wouldn’t bet on LiveView for mobile apps just yet.

#Flutter for web dev full#

Unless you can go full Firebase but that comes with its own limitations.Īlso, if web is involved, Flutter Web is a bad, bad framework. Is maintaining the Elixir backend your only problem? Is there any other issues related to Elixir that made you regret your decision? Because if there isn’t, then whatever backend you decide to have you will have to maintain it. If I could I would really prefer to just use Liveview and stick with that but it feels wrong and limiting for what I aspire this thing to be.Īnyways, would love to hear everyone’s thoughts on this. I know the Elixir bias is there but mine is too haha. I really love the idea of this app and I can see the future of it but I feel that the flutter elixir combo isn’t the way until I get it off the ground.įor other MVP (and beyond) peeps in the space, I really need your advice on what to do.

#Flutter for web dev Offline#

I fear that if I don’t put it on the app stores, and potentially offline ability it won’t even have a chance. I’m only one person and I want to put this milestone of the project.

A more brilliant option than in my list.

I’ve already written a significant version in Svelte but decided to drop it as well because I was thinking I can have all 3 with Flutter.

Use the JS ecosystem, make it into a PWA, and find a way to put it into the stores.

Although I really want offline mode and if I want that, then why bother doing this.

Pick up the old liveview code and somehow make it so I can turn this into an app.

Not scalable but good enough for starters I guess.

Drop the elixir backend and go all in with flutter and a BaaS-like pocketbase until it’s off the ground and just have mobile apps only.

U: feel like I’m at the point that I have a few routes in my mind: You can take a look at the ‘MVP’ so you can see the basic specs of what I’m trying to do. A way for you to write thoughts from the ‘voices’ in your head. I’m a solo dev and throughout this time though I’m realizing that I really don’t like having to maintain an elixir backend with a Flutter mobile. I’ve learned Flutter and built a somewhat MVP of this app.