Simple Mobile Tools Fork: F-Droid Suite for Privacy Fans
Simple Mobile Tools Fork review: Fossify migration for Gallery, Contacts, Calendar, and Notes, plus Android 14–15 storage permissions and SAF limits.
App summary
- App
- Simple Mobile Tools Fork
- Developer
- Fossify community (community fork of Simple Mobile Tools)
- License
- GPL-3.0-only
- Version
- unknown (varies by forked app)
- Size
- unknown (varies by forked app)
- Price
- Free; no paid tier or subscription published for Fossify forks
The name on the package is misleading in a way that matters. There is no single “Simple Mobile Tools Fork” you can install once and forget. Fossify is a community project that maintains a family of separate Android apps — gallery, calendar, contacts, notes, clock, calculator, file manager — each with its own package name, its own version number, its own permission set, and its own release history. Treat it as one product and you will make bad decisions about updates, backups, and migration. Treat it as a suite of individually maintained apps and it holds up well.
That distinction runs through everything below. Fossify exists because the original Simple Mobile Tools project changed hands — ZipoApps acquired it in late 2023 — and a group of contributors decided to keep the code alive under a community banner. The fork is published under GPL-3.0, listed on F-Droid, and hosted at github.com/FossifyOrg and fossify.org. None of that makes it an official release from the original developer, and none of it guarantees that every app in the family is equally healthy.
What follows is a working guide rather than a feature tour. The interesting questions about Fossify are not “does it have a dark theme” but “will my notes survive the switch,” “which of these apps still gets commits,” and “what happens to folder access on Android 15.” Those are the questions this review answers.
One Project, Many APKs: What the Fossify Suite Actually Contains
Fossify ships everyday utilities as independent installs. The confirmed core covers a gallery, a calendar, contacts, notes, a clock, a calculator, and a file manager. Each one lands on your phone as its own app with its own icon, its own settings screen, and its own update cadence. Nothing is shared between them except the codebase lineage and the visual language. If you want to understand the catalog that hosts the fork, F-Droid explains how the open-source store handles repository setup and privacy-friendly browsing. For a lighter way to browse and manage the repositories that carry the fork, Droid-ify walks through the F-Droid client setup that has to happen before any app appears. If you prefer installing the fork directly from its release pages instead of waiting on a store, Obtainium covers the signature and split-APK checks that decide whether an update actually installs.
The practical upside is that you install only what you need. Someone who wants a gallery replacement does not drag a calendar and a calculator along with it. The practical downside is that questions with a single answer for most apps — what version is this, how big is it, what Android version does it need — have no suite-wide answer here. Version numbers, APK sizes, and minimum Android versions differ from app to app, and they change on different schedules.
Distribution is similarly per-app. F-Droid is the main channel, and the project also publishes builds through its GitHub releases. Which channels carry which app can vary, and a listing that exists for one Fossify app does not automatically exist for another. The official site at fossify.org is the index to check before you install anything, because it is the one place that reflects the project’s own view of what is currently shipping.
Maturity is uneven across the family, and that is expected for a fork maintained by volunteers. Some apps are in steady use and receive regular attention; others are closer to “compiles and works” than “polished.” The original suite covered more ground than the fork does today, and not every original app has a fully equivalent maintained replacement. If one specific app is the reason you are here, verify that app first and worry about the rest afterward.
Moving from Simple Mobile Tools to Fossify: Gallery, Contacts, Calendar, and Notes Migration
Migration happens one app at a time. There is no unified importer, no “restore from Simple Mobile Tools” button, and no shared account that carries your data across. Each Fossify app is a separate package with its own storage, so each one needs its own plan: export from the original, install the fork, import, verify, then clean up.
Installing a Fossify app does not pull data out of the original app automatically. Android does not let one app read another app’s private database, and the fork has no privileged access to the old package. Photos and other media that live in shared storage are the easy case, because they are already files on disk. App-private data — notes, contact records, calendar entries, settings — has to leave through whatever export the original app provides. Contacts can typically be exported to a .vcf file and calendars to .ics; notes apps in this family have generally offered some form of backup or plain-text export. Confirm the exact option in the version you are running before you touch anything.
The signature problem is what makes pre-migration export non-negotiable. Fossify builds are signed with different keys than the original Simple Mobile Tools builds, and Android refuses to install an update whose signature does not match the installed package. You get a signature conflict, and the fix is to uninstall the original app first. Uninstalling wipes that app’s private data. So the order is fixed: export, verify the export opens somewhere else, uninstall, install the fork, import. Anyone who installs first and uninstalls second loses whatever was not backed up.
Widgets, home screen shortcuts, and automation need rebuilding afterward. Widgets are bound to the specific package that provides them, so a calendar widget from the original app will not survive the switch even if the data does. Tasker profiles, MacroDroid macros, and any intent-based shortcuts that name the old package will need their targets updated. Backup jobs pointed at the old app’s folders need re-pointing too. Check the official listing for each app you migrate, because import and export support is a per-app property here, not a suite-wide guarantee.
There is one more wrinkle worth planning for: you generally cannot run the original and the fork side by side for the same app. Different package names would allow it in theory, but the practical result is two apps competing for the same default-handler slots, the same widget space, and the same folder conventions. Pick a cutover point per app, do it in one sitting, and keep the export file until you have confirmed the new app behaves.
Fossify vs Other Simple Mobile Tools Forks: Which One Still Gets Updates?
Fossify is one community fork of Simple Mobile Tools. It is not the same project as every other fork that appeared after the ZipoApps acquisition, and it does not inherit their work or share their release schedule. When people ask “which fork is actively maintained,” the honest answer is that the question has to be asked per app and per repository, not per brand.
Release cadence differs across the suite. A gallery app with an active maintainer might see several releases in a quarter while a calculator sits untouched for a year — and that is fine, because a calculator does not need much maintenance. The trap is assuming that a recent release for one Fossify app implies recent attention on all of them, or that an old release date on one app means the project is dying. Neither inference holds.
There is no suite-wide version number to quote. Each app carries its own version, its own APK size, and its own minimum Android version, and those numbers move independently. Anyone publishing a single “latest version” for the whole fork is guessing or generalizing from one app they happened to check.
Judging maintenance takes about five minutes per app. Look at the commit history on the project’s GitHub repository for that app, check the release tags and their dates, read whether recent issues got responses, and look at the F-Droid listing for the last-updated date and the version it is serving. Cross-check the official site, because a project can publish a build on GitHub before F-Droid finishes its own build and review cycle. If an app you depend on has been quiet for a long stretch and has open crash reports with no replies, that is your signal — not the health of the brand.
Fossify on Android 14 and 15: Storage Permissions, SAF, and File Manager Limits
No single minimum Android version is published for the whole suite. Compatibility is a property of each app, so check the official listing for the specific one you intend to install. An app that runs cleanly on Android 13 may or may not have been updated for the behavior changes in 14 and 15, and there is no shortcut around verifying it.
Scoped storage is where the difference shows up most. Since Android 11, apps cannot freely walk the filesystem; they get access to their own directories plus whatever the user grants. Gallery and File Manager therefore behave differently from older Simple Mobile Tools builds that assumed broad storage access. Expect to grant folder access through the Storage Access Framework picker, and expect the app to hold a persisted URI permission for the folders you choose rather than a blanket permission for all storage.
File managers sit in an awkward spot on modern Android. Full filesystem browsing generally requires the “All files access” permission, which Google Play restricts to a narrow set of app categories. That restriction is one reason distribution channel matters here: a build delivered through F-Droid is not subject to the same store policy as one delivered through Play, and the permission behavior you see may depend on which build you installed.
Distribution channel is not cosmetic. F-Droid builds from source and signs with its own key; GitHub releases are signed by the project. The two are not interchangeable, and you cannot swap between them without uninstalling. Confirm the build source before you draw conclusions about permission prompts, because a permission difference between two installs of “the same app” is often a difference between two build pipelines. For Android 14 and 15 support specifically, check the official site or the app’s own listing rather than assuming uniform behavior across the suite.
Is Fossify Safe to Install? Audits, Reproducible Builds, and Who Pays the Maintainers
The code is public and licensed GPL-3.0, which means anyone can read it, build it, and check what it does. The project states that its apps contain no ads and no trackers. That combination is the main reason people trust this fork over the post-acquisition original, and it is a real advantage — auditable code is a stronger claim than a privacy policy.
Audits are a different matter from auditability. No single security audit covering the fork suite as a whole has been published, and reproducible-build verification is tracked per app rather than per project. F-Droid’s metadata page for each app is where reproducible-build status appears, and that status can differ from one app to the next. If reproducible builds matter to your threat model, check the specific app’s F-Droid page and its GitHub release notes rather than assuming the whole suite is covered.
Funding is worth understanding before you depend on any of this. The apps are free, there is no paid tier, and there is no subscription revenue paying for maintenance. Support comes from the community — contributions, donations where offered, and volunteer time. That model works, but it means sustainability is a per-repository question. Look at whether the repository for the app you care about has recent activity and responsive maintainers, because that is the actual durability signal.
F-Droid distribution helps on the dependency side. F-Droid builds from source and excludes proprietary libraries, so a Fossify app installed from F-Droid avoids some of the binary blobs that can creep into store builds. It does not make every app identical in behavior. Privacy practices can still vary by app and by channel, so verify the specific build you are installing rather than trusting the brand as a whole.
Pricing & Plans
Fossify costs nothing. The free tier is the whole product: $0 per app, $0 for the entire suite, no account, no ads, no in-app purchases, and no upsell screen waiting after the third launch. There is no Pro tier at $4.99, no $1.99 monthly subscription, and no “supporter” SKU that unlocks features. The fact data lists the price as free with no paid tier or subscription published for the forks, and that matches what the project actually ships.
The paid tier, in the conventional sense, does not exist. What exists instead is optional donation, where the amount is whatever you decide, including zero. Some open-source Android projects sell a “donation” package on a store to fund development; Fossify’s model is closer to direct community support, and the specific arrangements live in the individual repositories rather than in a suite-wide price list.
The real cost is time. Migrating four apps means four export-import cycles, four uninstalls, and a pass over your widgets and automation afterward. Budget an evening if you use the suite heavily. That is not a hidden fee — it is the price of moving off an app whose signing key you cannot update over — but it is a cost, and pretending otherwise would be dishonest.
Compare that to the alternatives on the proprietary side. Google’s Files, Photos, Calendar, and Contacts are free at the point of use, funded by an account you sign into and whatever the surrounding ecosystem does with that. If you are leaving Fossify’s price tag out of the decision because “it’s all free anyway,” you are comparing two different currencies.
Who Should Use Fossify
- Android users who want a gallery, calendar, contacts, and notes app with no ad SDK and no account requirement. The confirmed core covers exactly these everyday utilities, and each one installs independently.
- People who were using Simple Mobile Tools and want to keep the interface they know without staying on the acquired codebase. The fork preserves the general shape of the original apps while the community maintains them.
- F-Droid users who already add repositories and sideload APKs. This is the native habitat for the project; the workflow will feel normal rather than adventurous.
- Users who want to pick and choose rather than adopt a platform. Because the suite is separate apps, you can take the file manager and skip the clock without any coupling.
- Anyone who values being able to read the source of a utility that touches their photos, contacts, and calendar. GPL-3.0 means the code is there to inspect.
Who Should Skip Fossify
- People who only install from Google Play and expect automatic updates. Fossify is distributed through F-Droid and the project’s own channels, and availability varies by app. If a store-only workflow is a hard requirement, this is the wrong suite.
- Anyone expecting one unified app with a single install and one settings screen. It is a family of separate APKs, and no amount of hoping will merge them.
- Non-technical users unwilling to sideload an APK or add an F-Droid repository. The setup is not difficult, but it is not a Play Store tap either.
- Users who need built-in cloud sync and cross-device backup. These are local-first utilities; syncing is something you arrange yourself with a file sync tool or a calendar/contacts account.
- People on Android versions the individual apps no longer support, or who need vendor-specific integrations like Samsung or Xiaomi cloud services. Check the per-app listing before committing, and do not expect OEM cloud hooks.
- Anyone expecting official Simple Mobile Tools branding, support channels, and release notes. This is a community fork, not the original product, and the support model reflects that.
Comparison with Alternatives
| Feature | Fossify suite | Simple Mobile Tools (original) | Google apps (Files, Photos, Calendar, Contacts) | Material Files + Etar/Notally |
|---|---|---|---|---|
| License | GPL-3.0, source public | Open source, now under ZipoApps ownership | Proprietary | Open source, per-app licenses |
| Price | $0, no paid tier | $0 with optional paid "Pro" unlocks on some apps | $0 with a Google account | $0 |
| Distribution | F-Droid, GitHub releases, varies per app | Google Play primarily | Google Play, preinstalled on many devices | F-Droid, GitHub |
| Ads and trackers | None stated by the project | Changed after acquisition; verify per app | Telemetry tied to account | None |
| Cloud sync | Not built in; arrange your own | Not built in | Built in and account-based | Not built in |
| Scope | Suite of separate apps | Suite of separate apps | Suite of separate apps | Single-purpose apps, mix and match |
| Migration friction | Per-app export, uninstall, reinstall | In-place updates, but ownership concerns | Low if already in the ecosystem | Per-app export, same as Fossify |
| Maintenance signal | Per app; check commits and F-Droid dates | Vendor-driven, opaque | Vendor-driven, regular | Per app; smaller maintainer pool |
The original Simple Mobile Tools is the obvious comparison and the weakest one. It wins on convenience — Play Store updates, familiar branding, no sideloading — and loses on the thing that pushed people away in the first place: the code now belongs to a company whose intentions the community did not trust. If you never cared about that, staying put is rational. If you did, the convenience argument is not persuasive.
Google’s apps are the honest alternative for anyone who values sync and polish over licensing. Photos, Files, Calendar, and Contacts are tightly integrated, backed up automatically, and available on every device you sign into. They are also proprietary, account-dependent, and not something you can audit. That trade is real in both directions, and nobody should pretend the free option is free of strings.
The best-of-breed F-Droid route — Material Files for file management, Etar for calendar, Notally for notes — is the most interesting competitor. It gets you the same licensing and distribution benefits with apps that are often more focused than a general-purpose suite. The cost is fragmentation: more installs, more migration cycles, more places for data to live, and no shared visual language. For a single use case, that is a fine trade. For someone replacing six apps at once, the suite approach is less work.
Verdict
Fossify is worth using, with conditions. The conditions are the whole review: verify the specific app rather than the brand, export your data before you uninstall anything, and check the build source and the maintenance status of the repository you are actually relying on. Do that and you get a set of ad-free, GPL-3.0 Android utilities that respect the fact that you own your photos, contacts, and notes. Skip it and you get a signature conflict, a lost notes database, and a vague sense of betrayal.
It is a good fit for people already comfortable with F-Droid, for refugees from the original Simple Mobile Tools who want the interface back without the ownership question, and for anyone who wants to replace one or two system apps with something auditable. It is a poor fit for store-only users, for people who want cloud sync built in, and for anyone who needs a single unified product with one settings screen and one update button.
The suite framing is not a technicality — it is the operating instruction. Fossify is not one app, and the moment you stop treating it as one, the migration, the update checks, and the permission questions all become manageable. Treat it as a monolith and it will fail you in small, annoying ways. Treat it as what it is — a collection of separately maintained tools from a community that picked up code someone else put down — and it earns its place on your phone.
Pros
- Open-source licensing allows public code review and community contributions
- Community-maintained after concerns about the original project's ownership change
- Covers a broad suite of everyday Android utilities rather than a single-purpose app
Cons
- Not a single monolithic app, so version, size, and features vary by forked app
- App maturity and maintenance activity can differ across the suite
- Users migrating from original Simple Mobile Tools apps may need to export/import data per app
The link goes straight to Fossify community (community fork of Simple Mobile Tools). We do not host app files.
Frequently asked questions
Is Simple Mobile Tools Fork free?
The recorded pricing model is Free; no paid tier or subscription published for Fossify forks.
What license does it use?
It is listed under GPL-3.0-only.
Where can I download the official version?
The official link points to https://github.com/FossifyOrg.