Why I built a 'dumb' reading app in the era of AI and Social Feeds

TL;DR: I built a reading app that intentionally lacks "features" (no store, no social, no accounts) and focused entirely on native iOS mechanics and file ownership. Here is why I think the "Universal App" approach is wrong for niche tools.

The Context

I’ve been building justRead, an EPUB reader for iOS. The eBook market is crowded with apps trying to be the next Netflix or Goodreads—pushing subscriptions, social algorithms, and proprietary ecosystems.

And AI.

I decided to go the opposite direction. I wanted to build a tool, not a platform. Here are the 3 controversial architectural decisions I made, and why I think they are the right business move for a solo founder.

1. The "No Import" Architecture (Files vs. Database)

The industry standard for retention is Lock-in. Apps want you to import books into their database so it's hard for you to leave.

• My Approach: I built the app to read directly from the user's iOS File System (iCloud Drive/On Device).
• The Technical Trade-off: This is harder to code than a standard SQL database import because you have to handle file permissions and cloud syncing states in real-time.
• The User Benefit: Users own their data. If they manage their library in Calibre on PC, it auto-syncs to the phone. No "Send to Device." No duplication.
• The Business Bet: Power users (my target niche) value ownership over convenience. They are tired of their books being held hostage.

2. Native SwiftUI vs. "Write Once, Run Everywhere"

As a solo dev, the logical choice was Flutter or React Native to hit iOS and Android simultaneously. I chose native SwiftUI.

• The Reasoning: In a utility app, "feel" is the product. The 200ms lag in a non-native interaction breaks the flow. I wanted to leverage native iOS behaviors (Haptics, Dynamic Type, System Animations) for free.
• The Result: The app has zero "learning curve" because it mimics Apple's own design language (Apple Books/Notes/Safari). It feels like from Apple.

3. "Dumb" Orientation (Ignoring the Accelerometer)

This is a small UX decision that highlights the philosophy. Most apps auto-rotate. I disabled auto-rotation by default.

• Why? Reading is a flow state. A user shifting in bed shouldn't trigger a layout change.
• The Lesson: Sometimes "smart" features are just interruptions. Giving users manual control (locking to portrait/landscape) is often better than trying to guess their intent with sensors.

The Ask

I’m currently in pre-TestFlight. I’m curious to hear from other devs:

Do you think prioritizing "User Ownership" (no database/lock-in) is a viable moat against major competitors, or am I just making it too easy for users to churn?

Do you think mimicking Apple design UI is better than creating a super-duper UI by yourself?

I wrote a deeper dive on these design choices here: Why We Built justRead This Way

Link to project: https://justread.app