An app? Nope. For notifications, there is open source alternatives to Google and Apple services but it is used in the apps side, not users side. Have a look on microG and Open GApps to flash in your Android device; it might help you.
If you are worried about your privacy, yes, you must get rid of Google Play Services. However a majors part of your apps may be broken as too much rely on this services and only in those services.
If you want apps to based on this layer of Google mess, have a look on some open spruce alternatives of your favorite apps. Maybe some of them won’t embed Google Play Services. But keep in mind you may lose some features like notifications from Google devices or fine tunes location.
You can have a look on microG or Open GApps for alternatives. However you may need to hack your device to flash them.
What you can do, for example:
- check if you can flash alternatives (possible to root and before unlock the boot loader)
- maybe check if you can flash another ROM ; projects list the compatible devices. Have a look on LineageOS, GrapheneOS or also /e/OS
Any ideas for E2E encrypted storage alternatives?
Just wanted to share for the common knowledge and the debate as I already saw here some “post open source” and content about rubbish licenses like SSPL or BSL 😉
Whatever the solution behind is, if you have the resources, move to something self-hosted. Open core or not, if that topic matters to you, you might need something you can own and control. BTW, have a look on Forgejo, Codeberg and Gitea: these are the solutions I see when people look for something FLOSS, not open core, and maybe self-hostable.
That is the reason why some developers are “full stack”. All computers are stacked 🤪
Yes you should definitely check before whether or not the device is supported. You can find it for LineageOS here: https://wiki.lineageos.org/devices/
You may also have a look on /e/OS: https://doc.e.foundation/devices
Maybe Futo should move to “post open source” like “open core” principles.
Today majority of standards rely on definition accepted by a majority of people since decades, i.e. the open source definition by the OSI (https://opensource.org/osd), the free / libre definition of the FSF (https://www.gnu.org/philosophy/free-sw.en.html), and the principles of ethical source by the OES (https://ethicalsource.dev/what-we-believe/). Trying to apply new definitions is very hazardous, will induce lack of consistency and may make people more confused.
However, like the OES did for ethical source licences, defining a new group of ideas / licences with associated values seems to be more interesting, like few years ago with “open core”, and also “copyfarleft” and “copyjustright”.
In a nutshell, why changing the rules of the game instead of creating a new game? 🙂
Pure jerks, clowns and morons. Trying to redefine definition of open source is crazy, insane and irrelevant.
You can for example have a look on the online resource below:
https://www.securemessagingapps.com/
It is very interesting with a big comparison grid between plenty of messaging solutions.
Anticipate technical debt and follow what Google recommends. In few words, use Kotlin and Compose.
However you should really have a look on Google guidelines. In more worlds: