What we do
Native iOS development, built directly on Apple's own frameworks. That mostly means two situations. Building an idea in Swift/SwiftUI from scratch. Or taking over a project that's already partway there and finishing it properly.
And websites, for the same kind of client. A studio, a product, a launch page: hand-written HTML, no page builders, no frameworks, nothing loaded from third parties. Fast on a phone, readable by a screen reader, and, when the brief allows it, something people stop to look at. This page is the example.
Projects
-
A match-3 on the screen of an old terminal, for iPhone. Free, works offline, no ads, no lives or timers, and fully playable with VoiceOver: every line is spoken, the whole game works by ear.
App Store About the game
The game is free and stays free. If it earned a coffee: Ko-fi or Plisio (crypto).
-
Our next iOS app. Details when it ships.
-
tenebrae.lat
Website · Live
This site. The opening scene is one hand-written WebGL shader lighting our own mark: no 3D library, no build step, about 10 KB of code. Zero cookies, zero analytics, nothing loaded from third parties, and it stands still when your system asks for reduced motion.
-
Apps and sites built or taken over for clients, under NDA, so nothing to show here. Ask through the form and we will tell you what we can.
How it works
- I
Consultation. Tell us what you have and what you need. Free, no obligation.
- II
Audit. If there's existing code, we go through it and tell you honestly what's worth keeping.
- III
Build. Native Swift/SwiftUI, real infrastructure, and no shortcuts that come back later.
- IV
Ship. App Store submission and the deploy pipeline to keep it running after launch.
FAQ
Can you fix a vibe-coded app?
Usually yes. Most vibe-coded prototypes hit the same handful of walls: no real backend and fragile authentication. On top of that, the code usually gets too fragile to touch safely, even for the tool that wrote it. We look at what you have first and tell you honestly whether it's worth keeping or faster to rebuild the broken parts.
Do you work with clients in Montenegro and Serbia?
Yes. Most of the work happens remotely, over email and calls. No office visit required.
What if my existing code is a mess?
That's the normal starting point for this kind of project, not a disqualifier. We read through it, tell you what's actually wrong, and fix that instead of rewriting everything by default.
How long does it take?
Depends entirely on scope. Book a consultation and you'll get a real timeline, not a generic estimate, once we've seen what you need.
Do I need an Apple Developer account already?
No. If you don't have one yet, we'll walk you through setting it up as part of the process.
Privacy
This site sets no cookies, runs no analytics and loads nothing from third parties. Nothing about your visit is stored, processed or used.
The contact form sends your message, and a reply address if you give one, to our mailbox. That is the only thing that leaves this page. It is used to answer you and for nothing else, and it is not kept on this server.
The web server keeps ordinary access logs for a short time, for security only. Links to the App Store, Ko-fi and Plisio lead to those companies' sites, with their own policies.
Accessibility
We build for VoiceOver first. Final Fortress is fully playable by ear, and this site is meant to be read in full with a screen reader: one heading outline, real lists, a skip link, a label on every field, and text sizes that follow your browser's setting. The only motion is the opening scene at the top; it stands still when your system asks for reduced motion, and it is decorative, so nothing is lost without it. The aim is WCAG 2.2 AA.
If something here or in our apps does not work with your assistive technology, tell us through the form above. You will get an answer within a few days.