Apps · mobile and web

From an idea to the app store.

Besides websites I design and build apps, for the phone and for the browser: with the backend, the release and the updates after it. You work with one person the whole way.

MyStandApp live on Google Play
MyStandApp on a phone: open mics near Linz on a map

01 · Mobile app

MyStandApp, the stage companion for comedians.

My own product, from the first sketch to the release on Google Play in October 2026. Comedians write and rate their jokes, build sets, time and record them on stage, and find the next open mic. Organizers run their shows in the same app.

MyStandAppFor Android, by help.earth
Live
Platform
Android, on Google Play
Built with
React Native, Expo and TypeScript
Backend
Firebase, with a database on the phone
Released
11 October 2026
My part
Design, code, backend and release
  • 177countries on Google Play
  • 20+features, from the first joke to the earnings report
  • 0ads
  • 1person, from the sketch to the store
A joke in MyStandApp with its status, rating and tags A set of eight jokes with its running time Going live: duration, recording and the set The mic map with open mics in Upper Austria Stats: jokes, sets, shows, stage time and earnings

01 · Write

Every joke in one place.

A status from draft to ready, a rating after each show and tags, so it is clear which jokes work.

02 · Build

Sets made from those jokes.

Drag them into order and see the running time against the slot you were given.

03 · Perform

On stage, a timer you can read.

A large countdown that turns red when the time is up, and a recording of the set at the same time.

04 · Find

The next open mic, on a map.

Open mics, showcases and competitions nearby, with sign-up in one tap. Organizers post their own shows and pick the lineup.

05 · Grow

Stage time, shows and earnings.

Milestones and stats over the months, and an earnings report for every show, ready as a PDF.

Screens from the app’s Google Play listing.

Under the hood

Built for basement clubs with no signal.

Everything is saved on the phone first and syncs as soon as there is signal again. Try it: switch the signal off, and the app keeps working.

Online. Every change reaches the backup a moment later.

Offline first

The database lives on the phone. The cloud is the backup, not the condition.

Encrypted before it syncs

Jokes, notes and earnings are encrypted on the phone, with a key for each account, before they go to the cloud.

Transcribed on the phone

A recorded set turns into text on the phone itself, even without a connection.

02 · Web app

The studio, where my clients run their own sites.

One admin for the websites I build for artists. Samantha Lackner adds a show on her phone, and it is on her site right away, marked up for Google as an event and ready to go to her fans by email.

The studioOn phone and computer
In use
Built with
Svelte and TypeScript
Data
Postgres on Supabase; every site sees only its own data
Hosting
Cloudflare, with pages rendered on the server
Sign-in
A link by email, or Google
Email
A newsletter with double opt-in
The studio on a phone: Samantha Lackner’s upcoming shows Adding a show: the venue fills in its address and time zone Announcing a show: the email her fans will receive
  • 1.7 MBher homepage, down from 6.8 MB once it was rendered on the server
  • < 1 minfrom her phone to her site
  • 0calls to me when she adds a show

Samantha’s studio, with her real shows.

What I build

Apps, with everything around them.

One person, the whole way.

You talk to the person who writes the code, from the first call to the update after the launch. No hand-offs, and nothing gets lost on the way.

Mobile apps

For Android and iPhone from one codebase, in React Native.

Web apps

Admin areas, booking tools and dashboards that run in any browser.

Backend

Logins, databases, file storage and email, set up so every user sees only their own data.

Release

Store listing, screenshots, privacy pages and Google’s review, until the app is live.

Care after the launch

Updates, crash reports and new versions, so the app keeps working on every new phone and every new Android.

How we start

From the first call to version 1.0.

  1. First callFree, by phone or video: what the app should do, for whom, and on which devices.
  2. Fixed offerScope, price and dates, in writing.
  3. PrototypeThe main screens as a clickable prototype, before the build starts.
  4. BuildIn steps, and you test each one on your own phone.
  5. Release and careStore, review and launch, then the updates.

Have an app in mind?

A few lines are enough: what it should do, who will use it and roughly when. The first call is free, and you get an answer within one working day.

Write to me

filip@mladenovic.studio · +43 677 61179566