DEV Community

איתמר וענונו
איתמר וענונו

Posted on Fully Autonomous

One app for Android, iPhone and desktop – when iPhone won't let you do the main thing

The core feature of my app, Focus 100, is reading the notifications of WhatsApp and email apps and turning requests into tasks. On Android that's a documented API (NotificationListenerService). On iPhone it doesn't exist: iOS doesn't let one app read another app's notifications. Period.

So how do you ship "the same product" on three platforms when one of them blocks the main feature? Here's what I did, as a non-programmer building with Claude Code.

1. One UI, three shells

The interface is a web app. On Android it runs inside a WebView in a Kotlin shell, which adds what only native can do: the notification listener, the microphone, the calendar. On iPhone and desktop the same web app runs in the browser and can be added to the home screen.

One UI means a feature I ship lands everywhere. The web app is in 15 languages now, and the Android update with all 15 is rolling out this week. My release checklist has a step that says exactly that: every update goes to all three.

2. Replace the missing input, don't fake it

On iPhone the app can't see your messages, so it gets them other ways:

  • Paste a message – the task appears with a due date and a drafted reply.
  • Import an exported chat (WhatsApp lets you export a chat as a file).
  • Tell the assistant – type or talk; "remind me to send Dan the quote on Thursday".

I say this limit out loud in every store text and every post. The worst thing would be an iPhone user installing it expecting magic.

3. Sync without an account

No account means no login and no password to leak. Sync between devices is optional and end-to-end encrypted – the server only holds data it can't read.

4. Watch out for the WebView traps

  • System font size. Some Android users have a huge system font; the WebView inherited it and the layout broke. The fix: cap the scaling at 115%.
  • Store review. A WebView app needs to prove it's more than a website. The native parts (notification reading, voice, calendar) are what make it an app – document them for the reviewer.
  • Privacy text per platform. Every permission you add must be in the privacy page before you submit. I learned that from a rejection.

5. The App Store version

A native iPhone version is coming soon. It still won't read other apps' notifications – that's not something any App Store app can do – but it gets the same UI, sync, voice and assistant. One thing reviewers care about: if user content goes to a third-party AI service, say so clearly, in the app and in the review notes. Mine goes to Claude by Anthropic, isn't stored and isn't used for training, and the app says so.

The takeaway

Don't hide the platform gap. Design a different input for the weaker platform and keep the output – the task list, the drafts, the assistant – identical. Users understand limits; they don't forgive surprises.

How do you handle features that exist on only one platform?

I'm the developer of Focus 100 (free, no account, no ads): https://focus100-il.netlify.app/get?ref=devto-3platforms

AI disclosure: written by an AI agent from my own project notes.

Top comments (0)