The core argument
Ali's case rests on three points:
- Setup cost: Android Studio is heavy, and building for Apple platforms means using a Mac. A code editor such as VS Code and a browser will get a web beginner going.
- Distribution friction: Each native platform has its own signing, testing and registration hurdles. A static website can go live with a
git push. - Skill transfer: One backend can serve both web and mobile clients. Tools like Electron, Tauri and Capacitor let web skills carry over to desktop and mobile.
Each point holds up in a qualified form. None of them makes web development a prerequisite. The conclusion that fits the evidence is narrower: web-first is a good default for someone who hasn't picked a platform, and a poor one for someone with a specific native project in mind. Ali says as much in his closing lines, where he tells people set on Android to go ahead.
Hardware: Android is heavier, but check the details
Google's Android Studio requirements separate the IDE alone from the IDE plus the emulator. On Windows, the figures are 8 GB of RAM minimum for Studio alone, 16 GB for Studio and the emulator, and 32 GB recommended. Disk needs are 8 GB free for Studio and 16 GB with the emulator, and Google recommends an SSD of 32 GB or more.
That supports Ali's point that Android tooling can strain a modest laptop. Two caveats apply:
- Not every Android project needs the emulator. Testing on a physical phone changes the math.
- Lag depends on the machine and the project, so it isn't universal.
On Apple, local Xcode development does require a Mac. Apple's documentation says you download Xcode from the Mac App Store, and it states that membership isn't required to start building and testing on your own devices. The $99 per year Apple Developer Program applies when you're ready to distribute. It provides access to TestFlight, App Store Connect and certificates. A beginner can learn Swift without paying Apple a cent, but needs the Mac.
Distribution: real friction, with caveats
Google Play testing
Google's Play Console help states that personal accounts created after 13 November 2023 must run a closed test before applying for production access. The test needs at least 12 testers who have stayed opted in continuously for 14 days.
Meeting that bar only lets you apply. Google says review usually takes seven days or less. It adds that you may be asked to keep testing if you have fewer than 12 testers or the testers weren't engaged enough. It also says a tester who opts out and back in has to complete a consecutive 14 days to count.
This rule targets personal accounts, not all Android developers. Organization accounts aren't covered.
Android developer verification
This is the most time-sensitive part of the story, and it is easy to overstate. Google's Android Developers Blog says on September 30, 2026, app registration becomes required for participating stores in Brazil, Indonesia, Singapore, and Thailand. Google also states that unregistered apps can be sideloaded with Android Debug Bridge (adb) or an advanced flow. The company plans to expand the requirement globally in 2027 and beyond.
Third-party coverage adds detail on scope:
- One report lists seven participating stores: Google Play, HONOR App Market, OPPO App Market, Samsung Galaxy Store, Palm Store (Transsion), V-Appstore (vivo), and GetApps (Xiaomi).
- A September explainer from Foresight Mobile reads Google's FAQ as meaning that, in the four countries, the deadline applies only to the participating stores. An APK delivered by direct download, MDM or a partner store isn't covered until 2027.
- Another report says the first phase applies to certified devices running Android 7 or later.
So Ali's sentence is accurate if read carefully. It does not mean every Android install anywhere is blocked. A developer whose users are all outside those four countries wouldn't see a change on 30 September, though 2027 is coming.
Costs, per Google's guidance as summarized in the research: the Full Distribution account is $25 and mainly suits people distributing outside Play. The Limited Distribution account is free, needs no government ID, and covers up to 20 authorized devices. That 20-device cap is a hobbyist sharing option and not a limit on Android development itself.
Apple notarization
Ali writes that Mac apps shared outside the App Store need the paid program for notarization. I'd treat that claim cautiously. Apple's documentation describes notarization as a security check for software distributed outside the Mac App Store. The program page I could verify confirms only the $99 membership year and what it unlocks. I didn't confirm the exact membership conditions for every notarization workflow, so the safe summary is that serious Mac distribution realistically involves Apple's paid program.
Windows and SmartScreen
This is the part Windows developers will care about. Microsoft Learn says SmartScreen weighs two signals:
- publisher reputation, meaning whether the file is signed by a known publisher;
- file-hash reputation, meaning whether the specific file has been downloaded without signs of malicious behavior.
Even a signed new binary can show a warning until it builds reputation. Microsoft says there is no exact threshold, but it can take several weeks and hundreds of clean installs from a wide audience. (That is Microsoft's wording as relayed in its guidance. I'm not quoting the sentence directly.)
Microsoft's page also contains guidance that is more practical than the headline claim:
- Microsoft Store: Store-distributed apps are re-signed by Microsoft and never trigger SmartScreen download warnings.
- EV certificates: They no longer bypass SmartScreen. Microsoft says paying a premium for EV solely to avoid warnings is no longer justified.
- Artifact Signing: Formerly Trusted Signing, it is Microsoft's recommended signing service for non-Store distribution. Pricing starts at $9.99 a month, it needs no hardware token and it works with CI/CD such as GitHub Actions and Azure DevOps.
- Updates: Unsigned files start from zero reputation with every new version. Signed files can carry reputation forward if the same identity is used.
- Smart App Control: On Windows 11, Smart App Control can supersede SmartScreen reputation and blocks unsigned files that lack a positive reputation.
For a beginner shipping a first Windows utility, this is useful. Sign every release, keep a consistent signing identity, tell early testers about the possible prompt, and consider the Store.
The web side: easy, but not free of limits
GitHub's documentation backs the "push and share" claim for static sites. Pages publishes static files from a branch or via a GitHub Actions workflow, and GitHub Free accounts need a public repository. The docs also note:
- Pages doesn't support server-side languages such as PHP, Ruby or Python. It is a static host, not a backend.
- Published Pages sites are publicly available on the internet, even when the repository is private. Remove sensitive data before publishing.
- Changes can take up to 10 minutes to appear.
On hosting costs, Vercel describes its Hobby plan as free for personal projects, but restricted to personal, non-commercial use. Free tiers are fine for learning. They are not a promise of free production hosting.
How much web skill really transfers?
Web basics give you HTML, CSS, JavaScript, HTTP and client/server ideas. Those carry over, and a shared API can serve several client types. But each native target has its own UI frameworks and platform integration. Ali names Jetpack Compose, React Native and Flutter on Android, and design principles overlap only partly.
The cross-platform tools show both the promise and the limits:
- Electron: Its documentation says it builds desktop apps for macOS, Windows and Linux using HTML, CSS and JavaScript with Node.js and native code. Visual Studio Code, Slack, Discord, Notion and Docker are on its list of apps. It also states that zipped Electron apps are usually around 80 to 100 MB. If a small disk footprint is a hard requirement, Electron's own docs say to use something else.
- Capacitor: Its documentation describes it as a native runtime that lets web-first apps run on iOS and Android, with plugins for native features. It doesn't remove the toolchains. Local Android builds still require Android Studio and the Android SDK, and iOS builds require macOS and Xcode.
- Tauri: Ali says a minimal Tauri app can be under 600 KB. I couldn't verify that figure against Tauri's documentation, so treat it as his claim.
The Windows angle is simple. Electron and Tauri are web-to-desktop routes for Windows apps. They'd still go through the signing and SmartScreen reputation process above.
A practical decision guide
- Start with web if you're undecided, want fast feedback, and like sharing projects by link. Use VS Code, a browser and GitHub Pages for a first site.
- Start with Android if your idea depends on phone features. Check your RAM against Google's 16 GB figure if you'll use the emulator, or test on a real device.
- Start with Apple platforms if you own a Mac. Xcode is free, and membership can wait until you distribute.
- Start with Windows desktop if your audience is on Windows. Plan for code signing early.
- Whichever you choose, expect platform-specific setup and release requirements.
The bottom line
Ali's advice is sound as a starting-point heuristic, and he states that it depends on interest. What the official documentation adds is a set of corrections: Apple development doesn't begin with a fee, Android verification is a staged rollout, and the Play testing rule applies to certain accounts. Web skills reduce duplication but don't remove native toolchains. For a beginner, the web is a low-risk way to learn, as long as you don't mistake it for a requirement.