← SELECTED WORK

01 / 03 · LIVE IOS PRODUCT

RUKNA

A live iOS product that turns photographed local timetables into editable schedules, adds anomaly checks and supports dependable daily tracking.

Rukna home screen with the day's five prayers logged and a 40-day streak
THE DAILY SURFACE · LIVE SCHEDULE AND TRACKING
STATUS
Live on the App Store
ROLE
Founder · design, engineering, distribution
OWNERSHIP
Solo, end to end
CONTEXT
Consumer iOS product
TIMELINE
2026 · v1.0.1 shipped July
PLATFORM
iOS 17+

01 · AT A GLANCE

  1. 01

    Solo-shipped a live subscription iOS product, concept to App Store release in one pair of hands.

  2. 02

    Review-before-save extraction: every value the system reads from an image is confirmed by the user before it becomes the live schedule.

  3. 03

    Trust as strategy: paid, with no ads, no location tracking and no data sale.

STATUS
Live iOS product
ROLE
Founder · design, engineering, distribution

02 · PRODUCT DEMONSTRATION

Two Rukna screens on a dark frame: the timetable scan and the live daily schedule
Product showcase, recorded on device: image import → extraction → review → live schedule and daily tracking. · LOADS YOUTUBE ON CLICKWATCH ON YOUTUBE ↗

03 · THE PROBLEM

Apps that compute prayer times by formula visibly disagree with the printed timetable a mosque actually follows: minutes off, key entries missing entirely. For the people who plan their day around that sheet, a wrong time is a real cost. Rukna makes the phone run on the published schedule itself rather than an approximation.

04 · THE PRODUCT

Photograph the timetable, the sheet on the wall, the PDF or the group-chat image. Extraction runs server-side and returns structured rows, anomaly checks flag suspicious values such as an entry out of sequence, and every row is reviewed and confirmed by the user before it becomes the live schedule that tracking, reminders and the morning alarm run on.

I own the product end to end: concept, product design, iOS app, backend, database, authentication, subscriptions, App Store submission and distribution.

The shipped product as its trust chain: capture, confirm, live use, consistency.

  1. STEP 01

  2. STEP 02

  3. STEP 03

  4. STEP 04

05 · KEY DECISIONS

  1. 01

    Review before save

    Every value the system reads from an image is confirmed by the user before it becomes the live schedule, because a wrong time is a real cost, not a UI bug.

  2. 02

    Trust as the business model

    A paid subscription with no ads, no location tracking and no data sale, so the product never has to monetise attention or trust.

  3. 03

    Server-side extraction with anomaly checks

    Suspicious rows are flagged for correction before review, so a poor photograph costs review time rather than silent errors.

06 · VERIFICATION AND OUTCOME

Rukna shipped v1.0.1 on the App Store in July 2026. It handles multi-week booklets, editable schedules, daily tracking with forgiving streaks, reminders and a dependable morning alarm. Confirmation is mandatory by design, so extraction quality costs review time rather than silent errors.

Swift 6 · SwiftUI (MVVM) on iOS 17+ · Supabase backend with server-side Edge Functions for extraction · subscriptions via StoreKit and Superwall · the morning alarm uses the system alarm framework introduced in iOS 26. Every layer designed, built and shipped by one person, directing frontier AI coding systems under explicit briefs and verifying the output at each step.

CONSTRAINTS, EVALUATION & LIMITS

  • iOS-only today, with no Android or web client.
  • Extraction quality tracks source-image legibility. Confirmation is mandatory by design, so a poor photo costs review time rather than silent errors.
  • Multi-week booklet layouts vary widely, so unusual formats can still need manual correction.
  • Early-stage distribution. No usage or revenue figures are published anywhere on this site.