Android app: Support connecting to self-hosted Fizzy instances

[benBeideman]

Description

The Fizzy Android app currently connects only to the hosted fizzy.app service. For those of us running self-hosted Fizzy instances (which the project explicitly supports and documents), there's no way to use the native Android app with our own server.

Request

One or both of the following would be hugely appreciated:

• Add a custom server URL option to the Android app's login screen, allowing users to point it at their self-hosted instance (similar to how apps like Bitwarden, Nextcloud, and Immich handle this)

• Open-source the Android client (or provide build instructions) so self-hosters can compile it against their own endpoint

Option 1 is obviously the simpler ask for end users. Option 2 would be consistent with the spirit of making the server source available and would let the community contribute mobile improvements.

Context

Fizzy's self-hosting story is excellent. Docker deployment works great, the web UI is responsive, and the API is solid. The missing piece is native mobile access for self-hosted users. Right now the workaround is using the mobile browser, which works but loses the benefits of a native app (notifications, smoother UX, home screen presence).

This seems like a natural extension of the self-hosting support that 37signals has already invested in.

Environment

Self-hosted Fizzy instance (Docker deployment)
Android 14+

[flavorjones]

@benBeideman The one big issue we'd need to fix for the mobile app to work well with self-hosted instances is push notifications. As a user, that's a feature I'd expect and it's not there right now. I haven't been involved much in the thinking there, at some point someone from the mobile team might jump in here and provide more information.