51–60 of 109 posts
First one is Maui, which is a cross-platform toolkit supporting iOS, Android, Mac, Windows, etc... This generates a native app on each platform. Second path is embedding a Blazor app in a Maui skin, so Electron like.
I agree with others saying native is the way to go.
If it's for a business? How much money do you have to throw away? Does the app pay for itself, or is it a cost centre? (99.9998% of the time, it's a cost centre.)
You really asked the most boring part of that question. Most of the answers below suggest that the app is defending its territory, etc. Malarkey.
Just like you're not winning the lottery, you're not writing a standalone app that can pay for itself.
Why? Hundreds of thousands of apps exist on each platform right now.
For your app to stand out enough to be successful it needs synergy with something. A web site, a service, a IRL business.../something/.
Tha says to me: do the cheapest possible thing. If you have React devs, use that. If you don't, find the alternative cheapest possible way. Flutter? Maybe. Nocode (like Glideapp, https://www.nocode.tech/category/app-builders)? Maybe.
Pick the fastest/cheapest way to get an app out to validate the concept. Once validated, then you'll have enough information to know what pain points you have, and what solutions you /really/ need.
Earlier quoted context omitted.
Always been interested in the idea of sharing code across the full stack. What do you find you can share the most? APIs / data models?
> What do you find you can share the most? Types.
I'm highly skeptical of code sharing for other scenarios, and rarely (never) have seen the effort worth the payoff.
Earlier quoted context omitted.
Nicer than Flutter's Dart too. The only problems with Compose Multiplatform are the lack of multiplatform libraries, and documentation, but JetBrains tells me that a new documentation site is due this summer.
But then you're in Android Studio land. Have fun when adb refuses to recognise your connected Anroid phone. I gave up and created a React web app optimised for phones.
Earlier quoted context omitted.
Always been interested in the idea of sharing code across the full stack. What do you find you can share the most? APIs / data models?
I made Tamagui (with much effort) to solve this, which has probably the best setup out there at the moment for sharing your UI code on the frontend: https://tamagui.dev For backend we're working on a starter kit that puts together all the pieces (there are a lot!) that's days from release, if you reach out on the Discord I can help get you on as a beta tester. It uses Supabase for data and auth, which seems to give t…
FYI, the Silkscreen font on the website is completely illegible at smaller sizes like in the menus. Looks like a rendering glitch. Might want to choose something a little more legible.
Neither. The developer experience for both is awful, especially after you've been spoiled to an amazing dev ex from RedwoodJS.
Flutter is an awesome developer experience and would probably also make sense for small team that needs to support many platforms. I think I would target flutter if I had to support desktop OS. React-native would probably be preferable if you are just doing iOS/Android/Web due to the maturity of the ecosystem and wide use in the industry.
Flutter's widget tree is an abomination.
Earlier quoted context omitted.
I made Tamagui (with much effort) to solve this, which has probably the best setup out there at the moment for sharing your UI code on the frontend: https://tamagui.dev For backend we're working on a starter kit that puts together all the pieces (there are a lot!) that's days from release, if you reach out on the Discord I can help get you on as a beta tester. It uses Supabase for data and auth, which seems to give t…
Looks really cool. FYI, the Silkscreen font on the website is completely illegible at smaller sizes like in the menus. Looks like a rendering glitch. Might want to choose something a little more legible.