this post was submitted on 02 Mar 2024
430 points (98.0% liked)

Open Source

31218 readers
240 users here now

All about open source! Feel free to ask questions, and share news, and interesting stuff!

Useful Links

Rules

Related Communities

Community icon from opensource.org, but we are not affiliated with them.

founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] aeharding 1 points 8 months ago (1 children)

There are absolutely reasons where a native app is worth it - I just don't think building your own backend or not factors into that decision much.

Maybe the point you are trying to make, is when you have enough resources/large enough company, having duplicate teams for each native app isn't that big of a deal? I agree financially, although is is harder to technically coordinate two teams with dual releases and implementing features twice, with twice the bugs, and it slows things down. (Maybe not a big deal to Bitwarden - their app featureset may be quite stable, IDK)

(Disclaimer - I've been on teams building kotlin/swift apps and also cross platform apps professionally, so this is my firsthand anecdotal experience.)

[–] theherk 2 points 8 months ago

I don’t disagree. I’m just saying the distribution of workload has an impact on what looks a good idea or too hard.