Client work

Built for StyloTech clients. Every technical detail below comes from the delivered project.

  • My MotoclubRef. CW-01
  • My FruitopiaRef. CW-02
  • Tasty Tum!Ref. CW-03
Client projectRef. CW-01

My Motoclub

Event access control, in the hands of the people on the gate.

Entries taken, cars scrutineered, licences issued, guests registered, and every admission settled at the gate by one signed QR scan — then printed as a wristband on the spot.

iOSAndroid
  • The My Motoclub event list with one round live: 1,248 of 1,600 admitted on a 78 percent capacity bar, and the next rounds below it.
    Live event list
  • The car registration form for an autocross round, filled in for a turbocharged four-wheel-drive entry with the transponder and the entry fee accepted.
    Registration form
  • A rider's entry pass for the live round — the QR the gate scans, with its ticket code, date and holder.
    Entry pass
Screens from the shipped Android build, running on a demo database of fictional riders and events.
Client projectRef. CW-02

My Fruitopia

A morning’s picking, ordered before the cut-off and followed to the door.

One list published each delivery morning, priced in the unit each item is actually sold in, ordered before a cut-off, and followed on a live map until the van reaches the door.

iOSAndroid

The App Store listing is still being published under the app’s current name. The app itself is built and running on both platforms.

  • The day’s list for 16 September, with the delivery date and a 2:30 PM cut-off above it: Alphonso mango at Rs 130 with 30 kg left, watermelon by the piece, avocado marked plenty, chilli by the pack.
    Today’s list
  • Order FR01003 on a map of Ébène Cybercity with the delivery address pinned, and a three-step timeline — confirmed, out for delivery, delivered — showing the seller has not set off yet.
    Live tracking
  • Alphonso mango at Rs 120 per kg with an only-30-kg-left warning, a note that the seller sells this one by the kilo, a quantity stepper and an add-to-order button carrying the running total.
    Product detail
Screens from the running app, captured by its own integration-test driver against a locally seeded database. An invented catalogue and invented orders — never production data.
Client projectRef. CW-03

Tasty Tum!

Street food sold on the days the grill is on, paid for outside the app, and followed to the door.

A day the kitchen declares, a menu that belongs to that day, a bank transfer the seller matches by hand, and a delivery each customer can watch arrive without seeing anybody else's.

iOSAndroid

The App Store listing is still being published under the app’s current name. The app itself is built and running on both platforms.

  • The next working date — Tuesday 15 September, 11:00 to 21:00, marked open, ordering closing in four hours — with the popular dishes priced in rupees, an upcoming street-food event and the other published dates below it.
    Working dates
  • Live delivery for order TT-2397 on a map of Curepipe: the courier’s approximate position, the customer’s own stop pinned, “you are stop 2, there is 1 delivery before yours”, an estimated arrival of 19:40, and a note that other customers stay anonymous.
    Live tracking
  • The Double Smash Burger at Rs 320: what is in it, its allergens, a required size choice with triple at +Rs 90, extras, and an add-to-cart button carrying the running total.
    Product detail
Screens from the running app on an Android device, talking to its own API against a locally seeded database. Invented dishes, invented orders, an invented delivery run — never production data.
  1. 01

    Discovery

    How the business really works, including what nobody wrote down.

    • Scope and priorities
    • Roles and journeys
    • Constraints and deadlines
    • What to leave out of v1
  2. 02

    Design

    Interface and prototype, usable before we build it.

    • Every screen in scope
    • Clickable prototype
    • Design system and tokens
    • Responsive per device class
  3. 03

    Architecture

    The decisions that are expensive to change later.

    • Data model and schema
    • API contracts
    • Technology choices, with reasons
    • Environments and backups
  4. 04

    Build

    Short cycles, with something working to look at throughout.

    • Staging from early on
    • Regular demos, visible backlog
    • Tests as part of the work
    • Documentation written live
  5. 05

    Launch

    Data migrated, people trained, and a way back if needed.

    • Production and cutover plan
    • Data migration
    • Handover and training
    • Monitoring and alerts
  6. 06

    Care

    Fixes, updates and what comes next.

    • An agreed response path
    • Security and dependency updates
    • Performance monitoring
    • A roadmap for what is next
Let's build together

Ready to build something?

Tell us what you need. You get an honest view of scope, approach and cost — no obligation.

Client work — StyloTech