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.)

I don’t really see how developing a backend or not has anything to do with the decision to build a native or cross platform app.

But for Bitwarden, the interface is a much smaller proportion.

Can you elaborate on that? Bitwarden’s apps use Bitwarden public API, similar to how the Voyager app uses Lemmy’s public API.

Everyone on this thread: I can recognize native apps when I see them 😤

Native apps when they see them:

React Native is just a fancy web browser wrapping with some helper APIs.

React native is not a browser. It uses native components.

So you’re going to maintain two separate code bases with two separate teams as a knee jerk reaction to using one of the worst cross platform frameworks out there…

For an app that does little more than display encrypted text in a list…

weird flex but ok ¯\_(ツ)_/¯

Yes!

If you upgrade, this should be fixed btw!

I haven’t seen any spam ¯\_(ツ)_/¯

Its a feature of Voyager (and other 3rd party apps)

Aaaand keyword blocked. Tired of this VC shit showing up on my feed.

Mods too next release :/