The way it is in lemmy-ui now is fine.

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 ¯\_(ツ)_/¯

But then again, how do you know that Lemmy allows for an optional space? I wasn’t able to find a definition

By testing on lemmy-ui. That is the ‘reference implementation’

You should open a big with thunder. The Lemmy spoiler allows optional space

Oh, that is really weird. I can reproduce that. I looked it up and found this issue report that sounds like the root problem: https://github.com/ionic-team/capacitor-plugins/issues/1466

Hi thanks for the write up!

1. This doesn’t happen on iOS, but should get more investigation

2. I think this is a matter of opinion. I personally prefer the Voyager compact mode. But I am biased. ;) You can tap and hold to get to the ellipse menu. You can also disable the large vote buttons in settings for more tap space.

3. You can block, view side bar etc by tap and hold on username/community name.

4. I don’t think this has been requested yet as a feature on Github.

5. That’s cool

7 Planned :)

8. Voyager has recovery in case of app crash, but doesn’t have a draft system.

10 planned but not yet :)

12, you can tap and hold to jump back up.

14, you should see a warning if you hit back by accident. If the comment is empty there is no warning because there is nothing composed.

15, you can set Voyager to open links in browser, instead of in-app

16, this is being worked on :)

Yeah, this. Remark, the markdown library Voyager uses, is very powerful but also extremely complex (it has to be, to deal with Markdown edge cases).

I made a bit of progress last week on a custom plugin but it’s a lot of work. There’s like 4 layers of parsing required.

I wish Lemmy used GFM spoilers, which just uses normal details and summary html tags. But alas.

It’s really annoying there’s no standard markdown syntax in common mark.

Some seeders rotate, so just let it sit for a while. I’ve had success after a few weeks of waiting. Works more often than you’d think.

Yeah, exposing what report goes to who in the create report API is my main problem with this proposal. You’re approaching this from a power user perspective.

This is trying to solve what having report reasons would solve. If you had admin report reasons and mod report reasons then users can focus on what is the problem with the reported content, rather than who it should go to (casual users dgaf and probably don’t even know the difference between an “instance admin” and a mod)

So I’m not a fan. Again, this feels like trying to fix a symptom of the problem (no report reasons)

Take a few minutes and look how any other site does it.

It is currently permanent (with option to show hidden in communities), but temporary is a good idea. I don’t think anyone has requested that on Github yet!

Edit: Added to github

You should make an issue on Voyager’s Github! I don’t think anyone’s requested that feature yet.

Edit: Added to github

Dismiss read? Like a button to hide read posts? Voyager has that too.

Thanks for tagging them, I wasn’t sure who to contact!

😬