Mobile app capabilities (Coming Soon)

An honest rundown of what your App Store app can do on a phone — what works today, what's coming later, and what this kind of app doesn't support yet.

Coming Soon — App Store publishing is in early access. Contact support to join the waitlist.

When you publish your OverSkill app to the App Store, it runs inside a native app shell — so it gets access to real phone features on top of everything your app already does. Here's an honest picture of what that shell can and can't do, so you know what to expect before you build a feature around it.

Everything below is for the App Store version of your app. For the from-the-browser version that works today, see Installing your app on iPhone and Android.

Works today

• Everything your web app already does — it's the exact same app, so every page, form, sign-in, and feature you built comes along unchanged.
• Camera — take photos and video and upload them.
• Photo library — let people choose existing photos and videos.
• Microphone — record and share audio.
• Location (while using the app) — show nearby or location-aware content while the app is open.
• Device motion — motion- and orientation-based features (tilt, shake, step-style interactions).
• Contacts — help people find and invite others they know.
• Sharing — send content from your app out to Messages, Mail, and other apps through the standard share sheet.
• Push notifications — rolling out together with App Store publishing. Reach people right on their home screen. (See the note below — push needs your app published with your Apple account connected.)

We detect which of these your app uses automatically and set up only the permissions it actually needs — Apple rejects apps that ask for permissions they don't use, so we keep it tight.

Coming later

These are on the roadmap for the native app shell, but not available in early access yet:

• Biometric app lock — require Face ID or Touch ID to open the app.
• Haptics — subtle vibration feedback on taps and actions.
• Better offline support — more of your app usable with no connection.
• App icon badges — the little red number on your app icon.
• Scheduled local reminders — notifications the app can schedule on the device itself.

Not yet supported

An App Store app of this type doesn't support these — if your idea depends on one of them, it isn't a fit for the mobile version yet:

• Bluetooth accessories — connecting to external Bluetooth hardware. Not yet supported.
• Apple Pay inside the app — see Selling in your mobile app for how payments actually work. Not yet supported.
• HealthKit — reading or writing Apple Health data. Not yet supported.
• Home-screen widgets — the small live tiles on the iPhone home screen. Not yet supported.

About push notifications

Push notifications on the App Store version work a little differently from the browser version. To send them, your app has to be published with your Apple account connected — you add a separate push key during the Connect step of the publish wizard (it's optional there, and clearly marked). Without that key, your app still publishes and works fine; it just won't send native push notifications until you add it.

If you only need notifications in the browser/installed-from-web version of your app, those work today and don't require any of this — see Push notifications in your app.

What to read next

• Publish to the App Store — the full overview
• Prepare your Apple Developer account — get set up first
• Selling in your mobile app — how payments work by country