Native app & Apple extensions
HappyDay
A SwiftUI app with local storage, sync, widgets, Live Activities, a Watch app and Screen Time integrations. From product idea to the App Store and further iterations.
Swift · SwiftUI · iOS
How I work
with iOS.
I design and build native iOS apps, from the first interaction to the App Store. My work brings together product thinking, SwiftUI and the wider Apple platform.
Built in practice
Three products. Different engineering questions.
From my own consumer apps to a system for a client. These projects show where I have put iOS to work.
Camera & image processing
InFrame
An iPhone app that uses the front and rear cameras in sequence and combines the photos on the device. Including photo library access, location, purchases and ad consent.
Mobile apps & backend
Melles MCMF
A client project: visitor apps, a separate iOS scanner app, a management dashboard and backend. Developed through short feedback cycles with the client and users.
My technical experience
APIs by project.
Swipe across to compare the projects.
| Area | HappyDay | InFrame | Melles MCMF |
|---|---|---|---|
Interface |
|
|
|
Data |
|
|
|
Apple platform |
| Not used in this project |
|
Camera & media |
|
|
|
Purchases |
|
|
|
Intelligence |
| Not used in this project | Not used in this project |
Other SDKs |
|
|
|
Architecture & Swift
How I structure the code.
Patterns from HappyDay and MCMF.
Views, state and product logic
Screen state in view models; calculations and decision rules in plain Swift types that can be tested without a view.
HappyDay · NowCalendarModel / NowLoggingWindowTestable dependencies
Inject time, Calendar and UserDefaults so timers and date rules can be tested with controlled inputs.
HappyDay · NowViewModelTestsConcurrency with clear boundaries
HappyDay sync runs in an actor. MCMF uses dedicated API clients with async/await and typed models.
HappyDay · SyncEngine / MCMF · APIClientShared data across targets
HappyDay shares storage through App Groups and reuses models and stores across iPhone, Apple Watch, Mac and extensions.
HappyDay · SharedStorage / ReminderStoreExample: the InFrame photo flow
- 01
Tap the shutter
SwiftUI · Interface
- 02
Capture & combine
AVFoundation · Product logic
- 03
Save the photo
Photos · Photo library
State
- Ready
- Capturing
- Combining
- Saved
From idea to app
From first idea to App Store.
Four steps from my projects. Something to see, try and improve at every stage.
- 01
Make it tangible.
An early flow or prototype gives us something concrete to react to.
HappyDay · early sketches
- 02
Make it work.
One working flow reveals what the idea needs under the hood.
MCMF · working prototype
- 03
Try it. Refine it.
Short feedback rounds with the client and users shape the next version.
MCMF · design iterations
- 04
Ship it.
Purchases, permissions and the App Store are part of the finished app.
HappyDay · on the App Store
Testing, debugging & release
It has to work beyond the demo.
I combine unit tests, device testing and user feedback. HappyDay includes unit tests and builds through Xcode Cloud; InFrame and HappyDay have been released on the App Store.
When something breaks: understand it first.
Make the issue reproducible, isolate where it occurs, and check the same situation again after the change. This keeps debugging focused.
What I look for
Product logic
Being able to check rules and calculations independently of the screen with unit tests.
Permissions
Including the path where someone declines access to the camera, photos or calendar.
Data & lifecycle
Loading and error handling, reopening the app and returning from the background.
On the device
The actual interaction, camera orientation and the behaviour of widgets and extensions.
The product and the engineering behind it
From a good idea to an app you can use.
I enjoy working on products where a clear user experience and thoughtful engineering decisions reinforce each other.