{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreickct3yxiedrujuscgipnrbat45plwgntvmodanmkxdnwxsrxeh7y",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mqdk7iotwj52"
  },
  "path": "/viewtopic.php?t=33590&p=276467#p276467",
  "publishedAt": "2026-07-11T00:12:02.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": "> Could be worthwhile to put out Pale Moon mobile apps that (at least initially) use webview on Android and webkit on Apple, simply to claim the space and be able to snuff out any counterfeits. Also, it could possibly give all of us something to use on mobile other than crappy Firefox or spying chromium apps for browsing. Some Pale Moon ideas could be possibly ported into them like canvas.poisondata, zero telemetry, bookmark and password syncing, maybe some of our good extensions could be ported to mobile for that purpose, etc. Also it would probably be a good way to make more search-generated income for the project as long as DDG was onboard with it. Also, the stats don't lie - the world is going to mobile and ditching desktop in a very big way - there are entire continents where Android has like 70% of the OS marketshare, and in rich Western countries iOS has got very large and growing OS marketshare.\n>\n> Something to think about.\n\nWell, if we follow that logic to its ultimate conclusion... we _could_ just call it a day and slap the Pale Moon branding on a Chromium browser. Kinda goes against the original point of the project, but Firefox is 3% of the market at this point... we'd probably make more money and attract more users porting Pale Moon ideas to our own Chromium fork at this point.\n\nIt worked out for Microsoft... they were trying to maintain their own Spartan codebase for Edge. Google kept making their life difficult with standards churn. They cautiously tried a Chromium version of Edge for Android only, that was able to sync passwords and bookmarks. It was somewhat successful, and eventually the Windows version was Chromium-based as well, mostly just focused on replacing Google's integrated services with Microsoft's.\n\nIt's like, if we make an Android version with a Chromium engine and it's successful, why keep maintaining the desktop version at all? It wouldn't make sense to maintain two codebases... maintaining a Chromium fork for Android is not an insignificant amount of work.\n\nI mean, in a strictly pragmatic sense, you're not wrong to point these things out, but I also kinda thought that wasn't what we were here for.\n\n* * *",
  "title": "Other/future projects • Re: is this Android build unauthorised?",
  "updatedAt": "2026-07-11T00:12:02.000Z"
}