Custom URL scheme for simpler configuration

Hi!

I've just started using YACReader (bought the iOS version) and YACReaderLibrary (via a docker image), and I'm already in love with the app. One of the best finds of this year!

However, setting this up and configuring multiple devices to connect to a remote library made me think the process could be improved. Like the QR code is a great idea, but I feel like it's a bit limited right now and could be improved to provide a far better onboarding experience for people connecting to a remote library via a mobile app.

If the mobile apps supported a custom URL scheme (yacreader://...) or universal links, scanning the code could potentially open the YACReader app and automatically navigate to the YACReaderLibrary import screen, with the proper server IP/hostname and port, making it way easier to get non tech-savvy people to connect to the library (they scan the code, and they can immediately browse the library, sync comics and read them).

Another technical solution would be to use a smart app banner on the homepage of the library server (the screen that lists the library), so when you visit this page from a mobile app for example, coming from scanning the QR code, then you're invited to download the app, and, since you can pass arguments to the app when clicking on such links, could immediately bring the user to the YACReaderLibrary connection screen.

Happy to try to contribute to this feature if it gets picked up

A couple of days ago I was thinking about a way to improve this, specially if you are trying to connect from outside your local network. Yeah, universal links could improve things, but I like to make the users aware that if the connection data changes they need to reconnect the apps, not sure if a universal link would be clear enough about this.

Well, universal links would at least save the burden of opening the app, choosing the right connection method and entering the IP address / port manually.

Then for sure, if the mobile device is not on the same network, you would have to handle the network error properly. Which you already do BTW, but just with a simple "could not connect to the server" modal dialog. With a dedicated screen that invites the user to check if they're on the same network (wifi on, no VPN) and the server is still running, that would make it a bit more beginner-friendly.

The ultimate solution being a cloud service that acts as a relay/proxy (like ngrok for instance), so everything transits over the internet and you abstract the user from network issues. But that's another story

Yeah, a dedicated server costs money and it isn't sustainable without a subscription.