Aleksandr Prostetsov · Batumi, Georgia

Indie iOS & macOS developer.
Shipped products, not a business card.

Below are real case studies: the problem I was solving, what I built, the stack, and a link to the App Store or GitHub. Each product shows how long the prototype took. I do the work myself.

01

Work

iOS · App Store

Three apps, all shipped under my own developer account.

HeartScape

Heart rate, stress, and sonic biofeedback in a single app.

Problem

Standard heart-rate apps give you a number but no feedback in the moment — you see the value, but you can't feel it.

Solution

Heart rate and stress measurement with bio-acoustic feedback: the sound adapts to your rhythm and gently guides it back to a healthy range.

How it shipped

  1. idea — biofeedback through sound
  2. MVP — heart rate + basic sonic engine
  3. stress index based on HRV
  4. App Store release

Stack

  • SwiftUI
  • AVAudioEngine
  • HealthKit
  • Core Motion
  • Combine
Open in App Store →

ScanPlate

AI food scanner and calorie counter — point the camera, get the breakdown and macros.

Problem

Manual food entry is the weakest link in every calorie tracker. Most people give up after two days.

Solution

Recognize the meal from a photo, estimate calories and macros, and keep a daily log. Minimum input, maximum result — tap the button, take a picture of the plate.

How it shipped

  1. idea — a calorie tracker without manual entry
  2. MVP — photo → recognition → macros
  3. history and daily goals
  4. App Store release

Stack

  • SwiftUI
  • Vision
  • AI vision API
  • SwiftData
Open in App Store →

BlinkSubs

A subscription tracker that keeps all of your subscriptions in one place — without bank access.

Problem

Subscriptions leak away in small amounts: $5 here, $9 there. A year later it adds up to a freelancer's monthly paycheck. Bank aggregators want way too many permissions for that.

Solution

A local subscription tracker: add them by hand or from email receipts, see monthly and yearly totals, and get reminders before each charge.

How it shipped

  1. idea — a local subscription tracker
  2. MVP — list view + monthly total
  3. reminders, currencies, categories
  4. App Store release

Stack

  • SwiftUI
  • SwiftData
  • UserNotifications
Open in App Store →

All three are published under my own developer account: apps.apple.com/developer/aleksandr-prostetsov

YouTube Suite · macOS

Three Mac apps for YouTube production. I built them for my own pipeline. Download the bundle or grab one at a time (Paddle + BYOK — coming soon).

Wow Image

Generate images and short clips for your content — directly on your Mac, using your own API key.

Problem

Web-based image generators are expensive, slow, and force you to bounce between tabs. For a batch of 10 thumbnails in a row, that kills your pace.

Solution

A native Mac app: a prompt or reference → images and short clips. Bring your own keys (BYOK), no markup on top of the provider's price.

How it shipped

  1. idea — a fast image/video pipeline on the Mac
  2. MVP — image generation through a BYOK key
  3. short clips, presets, history
  4. released as part of the YouTube Suite bundle

Stack

  • SwiftUI
  • AppKit
  • BYOK
  • image/video APIs
Download soon

Wow Voices

Paste your text → get a voiceover. Minimal UI, none of the extra knobs.

Problem

Most TTS services are overloaded with options — voice, emotion, style, speed, pauses. By the time you pick all of them, you forgot why you came. You just need one thing: text → file.

Solution

One window: a text field, a voice picker, a button. Get a wav/mp3 file. Bring your own keys, pick your own provider.

How it shipped

  1. idea — TTS without the extras
  2. MVP — one screen, one voice
  3. multiple providers via BYOK
  4. released as part of the YouTube Suite bundle

Stack

  • SwiftUI
  • AVFoundation
  • BYOK
  • TTS APIs
Download soon

YouTube CRM

Multiple channels, video editors, video progress, costs vs. revenue, P&L per channel.

Problem

Once you have more than one channel and a few contractors, Notion and Trello turn into a mess. Nobody actually knows which channel is profitable.

Solution

A CRM built specifically for YouTube production: videos with statuses, editors with rates, channel revenue via the Google Cloud API, and a P&L for every channel.

How it shipped

  1. idea — P&L per channel, not just in aggregate
  2. MVP — channels + videos + statuses
  3. editors, rates, production costs
  4. revenue via the Google Cloud API, P&L

Stack

  • SwiftUI
  • SwiftData
  • Google Cloud API
  • YouTube Data API
Download soon

Other projects

Open source and web — for the full picture.

BYOK Vault

A wallet for API keys: iOS, macOS, Android. Open source.

Problem

API keys live in Notes, in .env files, in chat messages. That's bad for security and bad for speed — the key you need is always on the wrong device.

Solution

A local vault with encryption and quick access. One UX across three platforms, source open so anyone can verify that keys never leave the device.

How it shipped

  1. idea — a cross-platform vault for API keys
  2. iOS MVP — local encryption, search
  3. ported to macOS and Android
  4. open-sourced on GitHub

Stack

  • Swift
  • SwiftUI
  • Kotlin
  • Keychain
  • Android Keystore
View on GitHub →

Cookbook PWA

An interactive cookbook with a built-in shopping list. Offline-first, installs like an app.

Problem

Recipes in the browser mean ten open tabs, ads, and a shopping list you can't find at the checkout. A native app for a cookbook is overkill.

Solution

A PWA: recipes with step-by-step instructions, an auto-generated shopping list, everything works offline. Installs on any device, updates instantly.

How it shipped

  1. idea — recipes + shopping list in one place
  2. MVP — recipes with portion scaling
  3. shopping list generated from selected recipes
  4. offline via service worker

Stack

  • vanilla JS
  • Service Worker
  • IndexedDB
  • Web App Manifest
Link soon
02

How I work

  1. 01

    I do the work myself

    The first thing a client checks: are you actually doing the work, or are you handing it off? Everything you see above I designed and built myself, from the idea to the App Store. No outsourcing, no agencies, no "team that's on call." If we talk, you're talking to the person doing the job.

  2. 02

    Understanding the task

    If a contractor never asks questions and just says "got it," they didn't get it — they'll build what they know how to build, not what you actually need. So I start with a short call or a written brief, ask questions, and play the task back to you in my own words. If you need real proof, I'll do a small paid proof-of-concept for a fixed fee. Before the main contract starts, both sides can see that we're solving the same problem.

  3. 03

    Deadlines and communication

    The third question: will you hit the deadline you committed to, and how often will I hear from you? On work days I'm reachable — I reply within the day, usually faster. If something slips, I tell you up front, not on the day of the deadline. One honest schedule adjustment early beats silence and a surprise at the end.

  4. 04

    Revisions

    The fourth question: does the freelancer think you're being difficult when you ask for changes? Revisions are part of the job, not a punishment. If I misread something, I fix it and don't make the same mistake twice. If a change goes outside the original scope, I'll tell you up front and propose how to price it. No drama, no "well, I built what we agreed on."

03

Contact

I'm open to interesting projects and ambitious ideas. If you have one, get in touch — I'd be glad to help bring it to life.