Database ownership and proposal

[ild0tt0re]

I saw that with the next updates we will be able to run Organized on our own server with our own database, giving us uncompromised control over all data and access.

Do you have some update?

Proposal

I saw that currently the project use google firebase.
I would like to propose supabase (the open source firebase alternative) as replacement to improve also the local development.

[rhahao]

Hi @ild0tt0re, thanks for reaching out. As of now, this task is not yet started. But Supabase is indeed a good alternative to explore. We will keep this in mind when we start working on that feature. Greetings!

[erykjj]

How is your system up-time? Are down-times frequent and properly alerted?

[rhahao]

Hello @erykjj, good question 😊Since the app is mainly working using local data, I would say it should be ~ 98.99%. If some maintenance has to be done on the server side, and some app features cannot be used, yes indeed, we will send notification to the users. Thank you.

[ux-git]

@erykjj as mentioned, the app works with a local database and not cloud-based, meaning even when down-time will happen, vast majority of features will still be fully usable – even meeting scheduling, PDF exporting, ministry timer and import from jw.org remain functional. Organized is built to not rely on the internet connection. Even for users in areas with poor internet connectivity, having internet access just a few times a week or even a month to sync data from jw.org and update schedules for their congregation is more than enough to then complete all necessary actions.

The only features that will not work during that short period of time are:

1. Data sync (across your devices and within congregation). By default, it happens every 5 minutes, meaning that in most cases the lack of connection won't even be noticed, all the entered data will be synced during the next 5 mins in case of short outages, or immediately after the connection is restored in case of outages longer than 5 minutes.
2. Login. The app won't log users out automatically, but if a user is trying to log in exactly during the outage time, they won't be able to do it and must simply wait a few mins.
3. Collaborative features. Features that require data to be shared with other users, will simply not be visible in the app, while in offline mode. For instance, sending reports to secretary, syncing public talk speakers between congregations, publishing schedules for others in your congregation, and managing roles and settings of other users will be temporarily unavailable. These features are typically used only a few times a month at most, so their temporary unavailability during a short outage will have minimal impact on the overall user experience.

To conclude: Even during downtime, most features will remain accessible, and no entered data will be lost. While some user-to-user features may be temporarily disabled, you can still work in the app without interruption. Once the connection is restored, everything will sync seamlessly.

[erykjj]

Thank you both for the answers. Obviously, no one would want an unexpected outage at monthly report time. So, a solid, well-maintained server is crucial.

Once you implement cart witnessing with daily/weekly scheduling/volunteering/cancellations (or territories), a solid sync is a must, or frustration will ensue.

Thanks again ;-)

[ux-git]

Sure! The app is designed to prevent any loss of information, even in the rare event of an outage. As mentioned earlier, the uptime has been stable and reliable so far.

If you'll have any other questions, feel free to ask 🙂