Explore real iOS, Android and web capabilities we have implemented in shipped applications. Interact with them, see how they work, and find the ones your business needs — then have us build your version.
Each of these is a live, interactive demonstration running in your browser. Nothing is a screenshot, and nothing is connected to a production system.
An optional app lock built on the device biometric API — Face ID, Touch ID or Android biometrics — with a passcode fallback and a settings toggle.
RevenueCat sits on top of StoreKit 2 and Google Play Billing: the store still processes every purchase, RevenueCat resolves it into an entitlement the app can check on any platform.
A conversational assistant scoped to the product’s own domain and data, with a deterministic fallback so the feature still answers when the model is unavailable.
Apple’s Vision framework running on the device — subject detection and image analysis that never uploads the photo.
Scheduled local notifications and remote push, with permission handling and a deep link that opens the exact screen the notification is about.
Interactive maps with pins, selection and area context, driven by the product’s own records.
Availability, slot selection, confirmation with a reference, and cancel / reschedule handling.
A real operations console — records, queues, status changes and role-gated controls.
Camera-based scanning that reads a code and continues straight into the workflow it identifies.
A WidgetKit extension plus an ActivityKit Live Activity that tracks an in-progress trip on the Lock Screen and Dynamic Island.
RevenueCat sits on top of Apple and Google billing — the stores still process every purchase, RevenueCat turns it into one entitlement your app can trust on either platform.
Verified in 12 shipped ShahInvents applications. RevenueCat does not replace Apple’s or Google’s billing systems — it manages entitlement state across them.
Filter by platform, search for what your business needs, and open any capability that has a demonstration attached.
61 capabilities · 48 demonstrated in a shipped app
Who the user is, and what they are allowed to see.
Supabase auth with email and magic-link sign-in, sessions stored in the device keychain on mobile.
Native Sign in with Apple, required by App Review whenever a third-party social login is offered.
OAuth sign-in through the Supabase auth provider chain.
An optional app lock built on the device biometric API — Face ID, Touch ID or Android biometrics — with a passcode fallback and a settings toggle.
Separate customer, staff and admin surfaces, enforced in the database with row-level security rather than only hidden in the UI.
Sessions and tokens held in the iOS keychain / Android encrypted storage, never in plain application storage.
Charging for the product — one-off, recurring, or gated.
RevenueCat sits on top of StoreKit 2 and Google Play Billing: the store still processes every purchase, RevenueCat resolves it into an entitlement the app can check on any platform.
Native StoreKit 2 on iOS and Google Play Billing on Android — products, offerings, purchase and restore flows.
Entitlement checks wrap the premium surfaces themselves, so a free account sees the locked state and an entitled account sees the feature — the same build, two experiences.
Stripe Checkout, subscription billing and webhook-driven account state for the web products.
Wallet-based checkout for physical goods and services — the payment sheet, not in-app purchase, which Apple requires for real-world goods.
Assistants, analysis and generation doing real work in the product.
A conversational assistant scoped to the product’s own domain and data, with a deterministic fallback so the feature still answers when the model is unavailable.
Apple’s Vision framework running on the device — subject detection and image analysis that never uploads the photo.
Long video analysed for the strongest moments, then cut, captioned and exported as platform-ready clips.
Extracting structured fields from receipts, forms, contracts and PDFs, with a human review step.
Ranked, explained suggestions generated from the user’s own activity and the product’s catalog.
Reaching users, and users reaching each other.
Scheduled local notifications and remote push, with permission handling and a deep link that opens the exact screen the notification is about.
Associated-domain universal links and Android app links that route a URL to the right in-app destination.
Transactional email and SMS on real triggers — confirmations, reminders and follow-up sequences.
Person-to-person messaging with presence, read state and history, on the same real-time infrastructure we already run.
Maps, geography and place-aware workflows.
Interactive maps with pins, selection and area context, driven by the product’s own records.
Foreground location with the permission flow the stores require, used for “near me” context.
Defined coverage regions that decide what a visitor is offered, and what happens outside the area.
Camera, photo, video, audio and file pipelines.
In-app camera with permission handling, capture, retake and immediate use of the resulting image.
The system photo picker, which reads a chosen image without requesting access to the whole library.
A processing pipeline that ingests long video and returns cut, captioned, downloadable clips.
Validated uploads with progress, previews and storage rules that keep one customer’s files away from another’s.
Calendars, bookings, forms and documents.
Availability, slot selection, confirmation with a reference, and cancel / reschedule handling.
Recurring local schedules that survive app restarts and fire without a server round trip.
Staged intake with per-field validation, error recovery and a submission the business actually receives.
The admin side — the console your team runs the business from.
A real operations console — records, queues, status changes and role-gated controls.
Lead and customer records with history, stage, notes and follow-up state.
KPI tiles and charts over live operational data, with date-range switching and drill-down.
Item records with levels, consumption history and reorder signals driven by real usage.
First-party event tracking feeding funnel and engagement views the business can act on.
A signed-in space where a customer sees their own records, history and documents — and nobody else’s.
A staff-side surface with its own permissions, queues and daily workflow.
Search, sync, offline behaviour and moving data in and out.
Instant search with multi-facet filters, sorting and a genuine empty state when nothing matches.
Database change streams pushed to every open client, so a change on one device appears on the others.
Local-first records that keep working with no signal and reconcile when the connection returns.
CSV and report exports scoped to a date range, formatted for finance and operations.
PostgreSQL with row-level security, so access rules live in the database rather than only in the client.
Hardware and OS integration on the phone itself.
Camera-based scanning that reads a code and continues straight into the workflow it identifies.
Impact and notification haptics on the moments that matter — confirmation, error, and success.
The system share sheet, so output leaves the app into Messages, Mail, Files or any installed app.
A WidgetKit extension plus an ActivityKit Live Activity that tracks an in-progress trip on the Lock Screen and Dynamic Island.
GameKit authentication and leaderboard submission in a native SpriteKit title.
System-driven light and dark themes, plus layouts that adapt from phone to tablet to desktop.
The other systems your business already runs.
Purpose-built API routes with validation, rate limiting and predictable error handling.
External data and services pulled into the product, with caching and graceful failure when a provider is down.
Trigger-based sequences that move a record through its lifecycle without someone remembering to do it.
A tick under “shipped in an app” means the capability was verified in the source of a real ShahInvents application. A dash means we build it on request but no current app demonstrates it — we would rather say so than pad the table.
Choose what your app should do and get a blueprint you can send us — with the demos that prove each piece already works.