Apple Platforms

Why I Dropped Android and Web to Go All-in on Apple: The Indie Developer's Dilemma

·3 min read

I spent years bouncing between stacks, tools, and shiny frameworks, trying to be a "full-stack, multiplatform, language-agnostic" developer.
It sounds smart on paper. Diversified. Flexible. Safe.
But it was a trap.

When I finally made the decision to go all-in on Apple platforms—Swift, SwiftUI, iOS, macOS, iPadOS—everything changed.
Focus kicked in. Flow returned.
I started building faster, designing better, and loving the process again.

Here's why I decided to focus on Apple and leave the rest behind:

1. It Just Feels Right

There's something deeply intuitive about building with SwiftUI.
Native UIs snap into place. Animations flow.
And everything just feels like it belongs together.

It's hard to explain, but if you know, you know.
I used to chase frameworks that tried to be everything for everyone.
Now, I build where things feel natural.

2. Better UX, Better Tools, Better Performance

Apple isn't perfect—no ecosystem is.
But the toolchain, performance, and consistency are unmatched when you stay native.

SwiftUI, CoreData, SwiftData, and Xcode previews let me build beautiful, responsive apps that feel finished.

When I compare that to my experience trying to unify Android + Web + Mobile with one codebase, it always ended in compromises.

I'm done compromising.

3. A Market That Values Quality

Let's not ignore the economics: iOS users tend to spend more.
They expect quality and are willing to pay for it.

That's not a dig at other platforms—it's just what the numbers show.

As a solo dev building indie products, I want to work in an environment where thoughtful design, speed, and polish actually matter.

4. I Chose Depth Over Breadth

I was spread thin, juggling multiple stacks and never feeling truly confident in any.
Once I gave myself permission to go deep—to focus on one ecosystem and own it—everything got better.

  • Less cognitive load
  • Better problem-solving
  • Stronger intuition

The decision to specialize wasn't limiting; it was liberating.

5. The Stack is Finally Indie-Friendly

Apple has quietly built a local-first, backend-optional environment.

SwiftUI + SwiftData + iCloud unlock a solo dev stack that feels complete.
Want to add AI? You can hook into a backend API without jumping through hoops.

  • No overengineered auth flows
  • No patchwork of third-party libraries just to store a few notes

For once, it feels like the platform is on our side.

What I Paused (Not Abandoned)

  • Android – Jetpack Compose is strong, but it never felt like home
  • React Native – Still a great tool for certain teams and use cases
  • Web apps – I still use Next.js when needed, especially for landing pages and company sites

This isn't about drawing hard lines or burning bridges.
It's about aligning your tools with your vision.
For me, Apple just fit better.

Final Thoughts

We live in a world of "do it all."
But if you're constantly switching hats, you rarely hit flow.

Sometimes, focus is the unfair advantage.

I didn't quit Android or Web out of frustration.
I just realized the kind of products I want to build—and the kind of developer I want to become—are best served by going all-in on one ecosystem.

For me, that ecosystem is Apple.

And I'm finally building like I mean it.