323
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 29 Apr 2024
323 points (100.0% liked)
Programming
17314 readers
82 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
I've used it before and it's got it's pros and cons. Ultimately the big thing is not all apps need to be the "killer app". Some apps are pretty simple, so a one size fits all can be nice. It's definitely not the same as developing natively, but for small teams/apps it's not too bad.
If you're prioritizing cost, you should probably already be building a web application imo. There's very few cases where I would recommend cheaping out and building a native app, it's just kind of unsound.
If you're prioritizing cost, you should probably already be building a web application imo. There's very few cases where I would recommend cheaping out and building a native app, it's just kind of unsound.
If you're prioritizing cost, you should probably already be building a web application imo. There's very few cases where I would recommend cheaping out and building a native app, it's just kind of unsound.
If you're prioritizing cost, you should probably already be building a web application imo. There's very few cases where I would recommend cheaping out and building a native app, it's just kind of unsound.
It looks like your reply got submitted multiple times.
I agree with you now about preference for web apps, but that was not the case when Google started pushing Flutter.
Looks like my Lemmy-client of choice did some retrying when I had poor connection, sorry about that.
I think trying to go cheap on native apps was always kind of a fool's errand, tbh. Cordova, Xamarin, React Native and so on - all pretty sub-par solutions leading to poor experience without actually materializing the desired savings.
Looks like my Lemmy-client of choice did some retrying when I had poor connection, sorry about that.
I think trying to go cheap on native apps was always kind of a fool's errand, tbh. Cordova, Xamarin, React Native and so on - all pretty sub-par solutions leading to poor experience without actually materializing the desired savings.
Looks like my Lemmy-client of choice did some retrying when I had poor connection, sorry about that.
I think trying to go cheap on native apps was always kind of a fool's errand, tbh. Cordova, Xamarin, React Native and so on - all pretty sub-par solutions leading to poor experience without actually materializing the desired savings.
If you're prioritizing cost, you should probably already be building a web application imo. There's very few cases where I would recommend cheaping out and building a native app, it's just kind of unsound.
If you're prioritizing cost, you should probably already be building a web application imo. There's very few cases where I would recommend cheaping out and building a native app, it's just kind of unsound.