Native device features
What your app can do on a real device today — haptics, share, photos, location, and push broadcasts — and what is not available yet.
Available today
| Feature | Notes |
|---|---|
| Haptics | Vibration / feedback styles |
| Share | System share sheet (or clipboard fallback on web) |
| Pick image | Photo library picker — not camera capture |
| Location | GPS with permission |
| Push broadcasts | Owners send from Backend → Broadcasts; app users opt in from a Notifications page |
Not available yet
Camera capture, scheduled local notifications, maps, biometrics, and arbitrary native modules are not exposed in Appify’s bridge today. See What Appify can't do.
Set up push broadcasts
- In Backend → Broadcasts, add a Notifications page and publish the app.
- In Release → Signing, connect an EAS project. Then open Release → Push Settings: Android needs the matching
google-services.jsonand FCM V1 credential, while iOS needs an APNs key in EAS. - Build a fresh native binary. Each user must open Notifications and grant the operating system permission before that installation can receive push.
- Compose the message, choose the page opened on tap, confirm the audience, and review Expo delivery receipts.
Ask Build to use them
Example: “On the success screen, trigger a success haptic and offer a Share button.” Preview on web may use fallbacks; export / EAS use native modules.