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.
For a Reddit/Lemmy app though I would still prefer images to load in the app itself, because it’s more seamless. For now Jerboa handles images and GIFV just like any other link.
RIF let’s you configure this, which is nice. For Jerboa I think the default should eventually be to load them in the app itself (RIF calls this “Native”).
Edit: Jerboa does already load the OP image in-app when you open the comments. I think that behavior shouldn’t change. It’s just when you open the image from the news feed that it opens it like a link currently.
Oh I understand completely how it works. I would just prefer that my links open in app so whatever I view on jerboa doesn’t end up in my browser history or especially my YouTube history.
Lack of in app browser is a big complaint from me.
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.
For a Reddit/Lemmy app though I would still prefer images to load in the app itself, because it’s more seamless. For now Jerboa handles images and GIFV just like any other link.
RIF let’s you configure this, which is nice. For Jerboa I think the default should eventually be to load them in the app itself (RIF calls this “Native”).
Edit: Jerboa does already load the OP image in-app when you open the comments. I think that behavior shouldn’t change. It’s just when you open the image from the news feed that it opens it like a link currently.
Oh I understand completely how it works. I would just prefer that my links open in app so whatever I view on jerboa doesn’t end up in my browser history or especially my YouTube history.