torturedllama 47 points 3 years ago

I've been using Jerboa so far. It's pretty nice. At first I was a bit sceptical because it seemed a little half baked. But it's growing on me. Also now that I've used it for a while I think it's relatively well rounded feature wise. It is quite minimal, but I think a lot of people probably like that. I think long term if other apps come up that are more similar to the existing 3rd party Reddit apps I will probably switch though.

My main issue so far is not being able to follow links to communities inside the app. I imagine this will probably be more difficult to implement than on Reddit because of federation, but hopefully apps can get that working eventually.

Also it can be difficult to add new communities from other servers even via search. Which is also a federation issue.

I also miss the features from Reddit Is Fun which let you choose which content is displayed in-app vs in a web browser. But that's only a minor annoyance so far.

I find I am getting used to the visual style of comments. I initially didn't like it, but it's growing on me.

save

path: 0 287774, hotness: undefined, score: 47, children: 7

mesamunefire 21 points 3 years ago

Yeah I'm looking to contribute so we can address some of the issues.

save

path: 0 287774 287795, hotness: undefined, score: 21, children: 2

dill 13 points 3 years ago

I was planning to open a pr this afternoon for adding adaptive icon support.

Edit: I did it! It was already implemented there were a few tags missing I added

save

path: 0 287774 287795 288971, hotness: undefined, score: 13, children: 1

Jode 4 points 3 years ago

Lack of in app browser is a big complaint from me.

save

path: 0 287774 290424, hotness: undefined, score: 4, children: 3

torturedllama 6 points 3 years ago

When you open a link from Jerboa it should open a mini in-app version of your main browser. If your default browser app is set to Firefox it will say "Powered by Firefox" and if it is Chrome it will say "Running in Chrome". UX wise it is very similar to having a bundled in-app browser. But the rendering is handled by your main browser.

I'm not up-to date with the story behind this, but my understanding is that new apps that want in-app browers should be implemented in this way. This seems to be the modern way of doing it. The reason for it I believe is mostly security. Your main browser app should be up-to-date on security patches and features, and if apps can just piggie back off that then they don't need to worry about shipping and patching their own in-app copy of the browser. Also it respects the user's choice of default browser. So if your default browser is Chrome it will use that for the in-app browser for all apps that work this way (which is quickly becoming most apps).

Another advantage of doing it this way is that when you use the "Open in Firefox" button it seems to just move the tab from one app to the other rather than reloading it, so it happens almost instantly.

save

path: 0 287774 290424 312226, hotness: undefined, score: 6, children: 2