FadeMyInk
Laser tattoo-removal tracker
Patient: their own programme, progress and aftercare
- Add a session photo and watch the on-device measurement
- Save the result and see the fade curve update
- Switch to the clinic role to see the same record from the other side
The guided demo runs on sample data in your browser — nothing is connected to a production system and no real transaction is processed. Where a real URL can be framed, the toolbar above switches to it and says so.
Capabilities you could commission.
Supabase auth with email and magic-link sign-in, sessions stored in the device keychain on mobile.
See it on its own →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.
See it on its own →Separate customer, staff and admin surfaces, enforced in the database with row-level security rather than only hidden in the UI.
See it on its own →Sessions and tokens held in the iOS keychain / Android encrypted storage, never in plain application storage.
See it on its own →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.
See it on its own →Native StoreKit 2 on iOS and Google Play Billing on Android — products, offerings, purchase and restore flows.
See it on its own →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.
See it on its own →Apple’s Vision framework running on the device — subject detection and image analysis that never uploads the photo.
See it on its own →Scheduled local notifications and remote push, with permission handling and a deep link that opens the exact screen the notification is about.
See it on its own →Associated-domain universal links and Android app links that route a URL to the right in-app destination.
See it on its own →In-app camera with permission handling, capture, retake and immediate use of the resulting image.
See it on its own →The system photo picker, which reads a chosen image without requesting access to the whole library.
See it on its own →Validated uploads with progress, previews and storage rules that keep one customer’s files away from another’s.
See it on its own →Availability, slot selection, confirmation with a reference, and cancel / reschedule handling.
See it on its own →Recurring local schedules that survive app restarts and fire without a server round trip.
See it on its own →Staged intake with per-field validation, error recovery and a submission the business actually receives.
See it on its own →A real operations console — records, queues, status changes and role-gated controls.
See it on its own →A signed-in space where a customer sees their own records, history and documents — and nobody else’s.
See it on its own →A staff-side surface with its own permissions, queues and daily workflow.
See it on its own →Database change streams pushed to every open client, so a change on one device appears on the others.
See it on its own →PostgreSQL with row-level security, so access rules live in the database rather than only in the client.
See it on its own →Impact and notification haptics on the moments that matter — confirmation, error, and success.
See it on its own →The system share sheet, so output leaves the app into Messages, Mail, Files or any installed app.
See it on its own →What this product exists to fix.
Tattoo removal takes a year or more across many sessions. Patients cannot tell whether it is working, and clinics have nothing objective to show them — just two photos taken in different light.
Photograph each session, measure it on the device, and plot the fade curve. Patient and clinic look at the same number instead of arguing about a memory.
The implementation, at a level we can share.
- ✓Image analysis runs on the device — the measurement is uploaded, the photograph need not be
- ✓Separate patient and clinic surfaces over one record, enforced in the database
- ✓Session reminders scheduled locally around the healing interval
- ✓Digitises an issued US patent held by the studio’s founder
A capability-level overview. Endpoints, credentials, internal architecture and client-specific code stay private.
The same architecture, other industries.
Don’t copy the app — copy the capability. Every workflow above can be rebuilt around your business, your data and your users.
We can build your version of it.
Everything in this demo is a capability we can adapt, redesign or rebuild for your company — on its own, or combined with others into a single product.
Other products you can use right now.
You don’t have to build FadeMyInk.
We can adapt individual features, workflows, interfaces or the whole system to your business.