← Back/Case study · iOS app

Snaptek 5.0

I wanted a better way to capture and organize things from everyday life, so I designed and built it myself. Snaptek started in April as a way to turn screenshots into notes you can find again. Five months and 369 commits later, version 5.0 is live on the App Store.

Role
Founder, product owner, product designer and SwiftUI developer
Timeline
26 Apr – 23 Sep 2026
Platforms
iPhone, iPad, Apple Watch, Chrome
Status
5.0 is live
Home in Electric
Home in Grape
Home in Fuchsia

In 60 seconds

Role
Founder, product owner, product designer and SwiftUI developer
Timeline
26 Apr to 23 Sep 2026
Team
Two founders: I design and build iPhone, iPad and Apple Watch, and Malak builds Android

The challenge

What I wanted to keep ended up scattered: screenshots and posts saved on different platforms, articles, trip plans and spending I could not track. I remembered the thing, but not where I had saved it.

The insight

My hypothesis was that a contextual capture system could bring those together: a notebook that takes what I would otherwise screenshot and files it where I can find it again.

What I did

I designed and built it myself in SwiftUI, from a screenshot organiser in April to version 5.0 in September. Snaptek is an independently built product, so I treated myself as both the product owner and the initial user.

5.0

Live on the App Store, with a Chrome extension

Shipped · Quantitative

1

User so far, the designer. No usage or validation claims are made

Not yet tested · None

  1. 01

    Think

    Screenshots, posts, trips and spending, all scattered.

  2. 02

    Design

    Sketches of Home, folders and colour.

  3. 03

    Prototype

    Mock first in SwiftUI previews, approved in the Xcode canvas.

  4. 04

    Build

    SwiftUI for iPhone, iPad and Apple Watch.

  5. 05

    Ship

    5.0 is live on the App Store.

  6. 06

    Iterate

    Eight turns, from Screena to Vibe.

Problem

I built it to fix my own problems.

I love technology. I read about it and about design constantly, and I follow the tech news. I also travel a lot and love planning a trip. Every one of those habits leaves something behind, and for years I kept losing it.

01

Where did my money go?

I had trouble tracking my spending and could never quite see where my money was going.

02

Where did I save that?

Screenshots and posts saved on different platforms. I remembered the thing, but not where I had saved it.

03

That article, that design

What I wanted to keep from all that reading ended up scattered.

04

The trip in my head

Every trip plan was one more thing to save and find again.

Hypothesis

A contextual capture system could bring them together.

Two of them hurt most. I had trouble tracking my spending, and I could not remember where I had saved a screenshot or a post, because each platform kept its own pile.

So I built the app I wanted: a notebook that takes what I would otherwise screenshot, files it where I can find it again, and keeps track of what I spend.

A selfie under Tokyo Tower at night
A portrait in front of a ferris wheel
A portrait in front of a yellow and green ship

From the road.

Product

Let the app do the filing.

The first version was called Screena. You take a screenshot, share it to the app, and it files the picture as a card with a title, a place, a date and tags. No typing, no sorting.

Day one had three tabs, Recent, Folders and Settings, and one promise on the welcome screen: “Turn screenshots into organized knowledge.”

Sketch: take a screenshot, share it, the app reads it, it lands in a collection
Sketch, redrawn for this case study

Design decisions

What a note is, how folders work, what it reads, where AI shows up, what costs money.

01 · What a note is

A screenshot is a picture, not a note.

Screenshots are how most of us save things: a recipe from Instagram, a flight confirmation, a café someone posted. It sits in the camera roll with thousands of others, and when you need it, you scroll.

A recipe wants ingredients and steps, a workout wants sets, a medication wants a schedule. So Snaptek stopped being a screenshot organiser and became a notebook of note types, each with its own shape.

Real screens from the build of 4 May.

Real screens from the 4 May build: Recent, Collections and Recipes

02 · How folders work

Home, and a face for every collection.

Sketch of three Home directions: a list, a grid of tiles, and cards with this week
Sketch, redrawn for this case study

Three directions for Home: a plain list had nothing to look at, a grid of tiles was too flat. Cards with a summary of your week won, because Home should tell you something before you tap.

Sketch of four folder shapes, ending in the notched cover
Sketch, redrawn for this case study

One folder shape for every collection, so the symbol and the colour do the talking. Papers peek out of a notched cover. Once it was right I froze it: only the colours change.

03 · Capturing without a screenshot

Saving shouldn't need a screenshot at all.

With the Chrome extension, you click the Snaptek button on any page, pick a collection, and it’s on your iPhone. A recipe arrives ready to cook, with ingredients, steps, times and servings.

The extension is live

Sketch: click the extension, pick a collection, it arrives on the iPhone
Sketch, redrawn for this case study

04 · Reading what you save

The words in a photo, the page behind a link.

Two decisions about what Snaptek does with a thing after you save it. Both are read back from the app and extension source, with the detail closed under each.

Words in a photo should be searchable.

What you need
A photo of a menu, a page or someone’s post is only a picture until you can find it by what it says.
What I decided
I read the text on the device, with Apple’s Vision framework, when you scan with the camera or pick a photo. Nothing is uploaded to do it. The text goes into the note, so Search finds the note by what the picture says, and any web address in it becomes a link.
What it costs
It is only as good as the photo, because there is no cloud pass to rescue a blurry one. If nothing is readable, the note is still saved, with a dated title and no text, instead of an error.
How it works
  • It runs on camera scans and photo-library picks, on expense screenshots and PDFs, and on scanned PDFs in document import. A PDF with its own text is read directly. OCR only steps in when the PDF has almost none, for up to 30 pages.
  • Scans ask Vision for 19 languages with automatic detection, Arabic and Chinese among them. Expense imports ask for four: English, Chinese (simplified and traditional) and Arabic, a narrower list than the scanner’s.
  • The result is tidied before it is saved. Lines are ordered top to bottom, paragraph breaks come from the gaps between lines, and hyphenated English words are rejoined. Arabic is left in the order Vision returns it.
  • On a social screenshot, interface text such as like counts, Follow, Reply and timestamps is stripped out and the platform is recognised. The title is the first line of what was read, cut at 60 characters, and a confidence level (high, medium or low) is stored with each scan.
  • Expenses found by OCR wait in a review inbox, with possible duplicates flagged, before they become entries.

A shared link should arrive looking like what it is.

What you need
A bare address tells you nothing a week later. It needs a title and a picture, and saving it must not make you wait for them.
What I decided
The share sheet opens straight away on a placeholder card. You pick where the link goes while the title, picture and description load, and the note is saved whether or not they arrive. From Chrome, the extension reads the page once, only after you click, and hands it to your iPhone through your own iCloud. A recipe page also carries its ingredients, steps and times.
What it costs
I depend on what each site publishes about itself. A page behind a login or a bot wall gives less, and X posts come through a third-party mirror rather than an official API. I read no prices or product details: a shopping link is saved like any other page.
How it works
  • In the app, the title and picture come from Apple’s link previews. In the share sheet, which has less room to work in, they come from the page’s own Open Graph tags. Each request has a time limit of 6 to 10 seconds.
  • YouTube, Instagram and Reddit also ask the site’s oEmbed endpoint. For YouTube I swap in the plain video still, because the share image has the play button drawn into it.
  • If a site refuses, the title falls back to the platform or the domain, such as Instagram Post or YouTube Video.
  • The extension reads the page title, description, preview image, icon, canonical address and, on a recipe page, the schema.org Recipe data: ingredients, steps, times and servings. The link, title and description are written as CloudKit encrypted fields. Offline saves wait in a queue of up to 100 items for 30 days, and the extension keeps a local record so the same page is not saved twice to the same collection.
  • If a recipe page has no structured data, the phone tries to read the page itself. Where a site blocks that, it stays a plain card.

05 · AI interactions

AI that stays on the device.

Inside the product, Apple Intelligence runs on the device, so the privacy promise stays true and there is no server bill on a feature people use all day.

The assistant’s reply resolves word by word out of a blur. The first typewriter made every answer read like a machine at work. Now nothing reflows under the reader, and Reduce Motion swaps it for a crossfade.

06 · Apple ecosystem

Home runs as itself at every size.

Home is never a special Duo screen. Folded, only the bars move. Opened up, the inner display keeps them horizontal. Around it, Snaptek works with Apple Health, adds widgets, Live Activities and Siri, and 5.0 syncs through the CloudKit mirror.

  • iPhone
  • iPad
  • Apple Watch
  • Apple Health
  • Widgets
  • Live Activities
  • Siri
  • Apple Intelligence
  • CloudKit sync
  • iPhone Duo
Three outer-display screens with the side rail: Home, Money and This week

07 · What is free, what is Pro

One Pro, kept on top of a free app.

How the free app and Pro divide today, read back from the code. This page says nothing about what it earns, because there is nothing here to back that up.

The free app does the main job. Pro adds on top.

What you need
To save things and find them again without paying, and to know clearly what paying adds.
What I decided
Reading and filing that happens on the device is free for everyone. Pro is what you add on top. There is one Pro, sold as three plans (quarterly, yearly or lifetime) with the same features, instead of tiers with different lists. I dropped the credits that cloud AI used to run on.
What it costs
Free users’ shared links all land in Recent, and the Chrome extension shows a locked screen that sends them back to the iPhone to upgrade. I also have to keep the Pro flag in step in three places: the app, the share sheet and the extension.

Free

  • Scanning and reading text in photos
  • Link previews from the share sheet
  • Sorting into the built-in collections
  • Recording a meeting
  • Your first colour, plus canvas and title face

Pro

  • Choosing the collection when you share a link
  • Saving from Chrome
  • iCloud sync
  • Changing colour afterwards, light or dark, app icon and app lock
  • AI note writing with Apple Intelligence
  • Translation
  • Meeting transcripts
  • Workout performance charts
  • Sharing a note as a file or an iCloud link
How it works
  • Purchases run through StoreKit, and only verified, active, non-revoked transactions unlock Pro. Older product IDs are still recognised so existing customers keep their access, but they are no longer offered.
  • Someone who owns Lifetime is not shown the subscriptions again, so they cannot pay twice for what they already have.
  • The share sheet and the extension cannot see the app’s purchases, so the app copies the Pro flag to them: into a small shared file for the share sheet and into iCloud for the extension. If the extension cannot read the flag, it lets the save through.
  • Two splits are deliberate. The first colour is free in onboarding and changing it later is Pro. Recording a meeting is free and transcribing it is Pro.

08 · One system

Rules that stuck.

  1. 01A warm off-white canvas with white cards.
  2. 02A dedicated card for each note type instead of one card for everything.
  3. 03Every button a glass capsule.
  4. 04Concentric corners: an inner corner is the outer radius minus the gap.
  5. 05In 5.0, colour stops being an accent and becomes the canvas.
The five system rules as swatches, from off-white canvas to colour as the canvas

What if the whole app wore your colour?

The canvas is the brand. Five colours, Ember, Electric, Grape, Fuchsia and Lime, each in vivid or calm, with wide or rounded titles, light or dark. Cards float on the colour like paper.

Sketch: the canvas is the brand, five colour swatches, vivid and calm
Sketch, redrawn for this case study

Pick a colour. The whole app wears it.

Five colours, each in two moods. Vivid puts the colour on the whole canvas. Calm keeps the off-white canvas and lets the colour live in the accents. Same screen, same notes. These are real screens from the 5.0 build on iPhone Duo’s outer display, and every combination is contrast-checked.

Colour: Ember
Snaptek Home on iPhone Duo in Ember, vivid

Screen recording, onboarding

Vivid and calm side by side: Home, workouts and settings

In the app the choice comes first. Onboarding asks for a colour before anything else, and swiping recolours the whole screen as each card settles. One glass capsule holds the colours, and the chosen dot opens into a pill with its name. Vivid or calm is the smaller choice, so it sits up by the wordmark instead of stacking another row above Continue.

Build

Eight turns.

Dates from the project history, April to September 2026.

  1. Apr 26v1.0

    Screena

    Screenshots in, organised cards out.

  2. Apr 30v1.5

    Typed notes

    Recipes, workouts, pills and expenses.

  3. May 3–7v2

    Everyday

    Apple Health, languages, currencies, AI Notes.

  4. May 10v3.0

    AI assistant

    A new Home, widgets and Live Activities.

  5. May 22v3.6

    Money

    Expenses grows into accounts, cards and transfers.

  6. Jul 15

    On the device

    The assistant moves to Apple Intelligence.

  7. Aug–Sepv4.2–4.4

    Craft

    A card per note type, glass buttons, concentric corners, Siri.

  8. Sep 235.0

    Vibe

    The whole app wears your colour.

Two founders.

Snaptek is built by two people. I design it and build the iPhone, iPad and Apple Watch apps, and Malak is developing the Android app.

Taipei · Product, design and iOS

Alhasan Hosni

Founder

Started Snaptek to fix his own problems with saving, finding and spending. Designs the product and builds the SwiftUI apps for iPhone, iPad and Apple Watch.

  • Product
  • Design
  • SwiftUI

Shipped

5.0 is out.

Snaptek 5.0 is out now on the App Store, and the Chrome extension is live. Android is next.

Five iPhones in five colours under the line “5.0 is out now”

Your life, in colour.

The Snaptek website opens the way the app does: the headline inflates into soft balloon letters, the icons build themselves, and butterflies land on them. It is the live hero from snaptek.app.

The hero of snaptek.app, live.

How I knew

Snaptek is an independently built product, so I treated myself as both the product owner and the initial user. I felt every one of these problems every week, so I never had to guess the pain. The limit is the same: it is one person's habits. This page makes no usage claims, only the story of what I built and why.

The May 2026 Home beside the September 5.0 Home in Ember calm

What I learned

What May taught September.

May’s Home was a list of rows. On the calm canvas, 5.0 leads with today’s cards, then your to-dos and your week, and the colour moves into the accents. Using it taught me these.

  • Money screens flashed wrong numbers while they loaded.

    Fixed in 4.4, the release called “Squashing Money Bugs”.

  • One card for every note type felt generic.

    Every type has its own card.

  • A streak shown as “0 days” beside fourteen dots wasn't understood.

    The streak was redesigned.

  • Cloud AI ran on credits.

    The assistant runs on the device with Apple Intelligence.

More detailsUnder the hoodHow one person builds with coding agents, the rules they work under, and the code behind the AI reply.

Two kinds of AI, kept apart

Around the product, I build with coding agents every day. That is how one person carries an app across iPhone, iPad, Watch and a browser extension. What makes it work is not the model. The repository tells the agent what good looks like before it writes a line: a token contract in DESIGN.md, and rules it has to follow.

The rules the agents work under

  • 01Ground every new surface in real product patterns first, then design.
  • 02The design system is the floor. An agent composes from the tokens, never invents a value or a one-off component.
  • 03Mock first in SwiftUI previews. Nothing enters the app until the mock is approved in the Xcode canvas.
  • 04AI output that reaches a user is a draft with a visible correction path, never a silent write.
  • 05If a check did not run, I do not say it passed.

The reply resolves. It doesn’t type.

Swift

The first AI reply used a typewriter, and every answer read like a machine at work. Now a single Text is laid out once and a custom TextRenderer resolves each word out of a blur. Nothing reflows under the reader, and Reduce Motion swaps it for a crossfade.

/// Reveals a reply one word at a time. The earlier typewriter added
/// characters one by one and made every reply read as a machine at work.
struct TypewriterBlurText: View {
    let text: String
    /// The vibe type role to set the text in. Wins over `font`.
    var role: VibeFont? = nil
    let color: Color
    /// False shows the text sharp at once. A reply that was read in an
    /// earlier session is a record, not an arrival, and must not perform
    /// again every time the chat is reopened or scrolled back into view.
    var animated: Bool = true

    @Environment(\.accessibilityReduceMotion) private var reduceMotion

    /// 0 is nothing revealed, 1 is every word sharp.
    @State private var progress: Double = 0
    @State private var words = WordRevealMap(text: "")
    /// Reduce Motion swaps the reveal for a crossfade.
    @State private var fade: Double = 1

    var body: some View {
        styled
            .multilineTextAlignment(.leading)
            .textRenderer(WordRevealRenderer(progress: progress, words: words))
            // …
    }
}
Next project

Talentera