Local Mock Mode & Cloud Storage Independence about spezitemplateapplication HOT 3 OPEN

Discussion wth @vishnuravi & Oliver: Maintaining a fork is a bit challenging. The entire application in the fork is the easiest for developers, it would be challenging for us to maintain. We should investigate how much the diff would be.

From a user's perspective a fork would be easier to be used.

from spezitemplateapplication.

To add some more context, by now we incorporated a feature flag to disable firebase completely. If so, it completely disables the Account module. We could resolve this issue by additionally configuring the account module with the MockUserIdPasswordAccoutnService (which is used within our previews) to have a Mock for most of the functionality the template app supports.
Apart from that, storage of HealthKit Data and Questionnaire data would need to be mocked (as we already do with the MockWebService?).

from spezitemplateapplication.

Yes, mocking the storage of HealthKit Data and Questionnaires can be done with the MockWebService. I could see a future where the web service actually mocks persistence and allows one to use it as a full local replacement to mock behaviour but that would require some additional work in that package which might actually be kind of interesting 🚀

from spezitemplateapplication.