Hey Max,
Sorry for the late response.
One possible future is we switch to Graphene.. Worth noting that Graphene is also Android.
we already modify Android and deactivate any explicit reporting to Google, though of course we can't completely guarantee it within google apps the user activates.
The most important is that, long-term, we are writing our own operating system from scratch, without any reference to Android. Graphene is a modified/forked Android (same as ours currently is).
What will that mean for application support? To me, a privacy focused Android derivative sounds more appealing than a custom OS
The nice thing about using graphene or another android fork would be the app compatibility and Dev community.
Getting people to program for a new OS sounds like an uphill battle.
Graphene behaves similarly to what you described. The user is in control of their own privacy. The profile feature is very useful in managing apps that require a lot of access.
FWIW running on android has its advantages from using the Google play (or other app repository) and optimizing apps. If you introduce another OS will developers need to make a separate app for daylightOS or will the android version of the app work?
Also please make the OS free-and-open-source. This will carry a lot of weight in your target audience.
šš»
of course, GrapheneOS is open source and this sort of thing is verifiable.
where is your source code published?
Would be cool to see a new OS, of course it's a huge task, but so is a 60FPS eink...
Can you download any app to the tablet or are there limitations.
You can. We use a modified android os for now. Meaning you can download most apps
I'm hoping that it would still be binary compatible with APK files either way. I could live with f-droid and likely no google services at this point. It would take a bit of effort but I'm nearly there.