Depends on your definition of “phone app”. I use it on my phone as an installed webapp (Add to home screen on iOS / Install on Android). Look and feel-wise, it’s indistinguishable from an “app” app. Only thing it lacks is system notifications (which may or may not be a dealbreaker for some).
Lemmy World runs an instance of it, but it’s locked to .world.
I run an unlocked hosted instance at https://tesseract.dubvee.org/ which is configured to allow login to any Lemmy server.
Selfhosting is also an option; I believe it also works fine from localhost (there used to be issues uploading images, but I think that went away as of 0.19.0).
Yeah, that’s me failing to update the readme. lol. Good catch.
The CORS handler / upload proxy was removed completely a good while ago (I think in 1.4.0 when I dropped support for 0.18.x API). I’ll make a note to myself to clean up the readme.
I also use it on mobile and have it installed as a web app. Firefox can occasionally be very finicky about which web apps are installable, but I had no issues with Tesseract. I assume on Chrome/etc it’s no problem at all.
Tesseract looks really nice
Only downsides i see are:
And none of them sound like a problem to me
Depends on your definition of “phone app”. I use it on my phone as an installed webapp (Add to home screen on iOS / Install on Android). Look and feel-wise, it’s indistinguishable from an “app” app. Only thing it lacks is system notifications (which may or may not be a dealbreaker for some).
Lemmy World runs an instance of it, but it’s locked to .world.
I run an unlocked hosted instance at https://tesseract.dubvee.org/ which is configured to allow login to any Lemmy server.
Selfhosting is also an option; I believe it also works fine from localhost (there used to be issues uploading images, but I think that went away as of 0.19.0).
Installed webapps it what i meant with options so its neat that we booth reached the same conclusion
About localhost: at least in the readme there still is mention of image upload issues because of the cors handler
Yeah, that’s me failing to update the readme. lol. Good catch.
The CORS handler / upload proxy was removed completely a good while ago (I think in 1.4.0 when I dropped support for 0.18.x API). I’ll make a note to myself to clean up the readme.
I also use it on mobile and have it installed as a web app. Firefox can occasionally be very finicky about which web apps are installable, but I had no issues with Tesseract. I assume on Chrome/etc it’s no problem at all.