Apps, end to end
iOS, iPadOS, macOS and the web. Concept, interface, data model, backend and the shipped binary. One head holding the whole picture.
Paddockware is Stefan Zechmeister. More than two decades at the sharp end of large-scale software delivery, and a workshop where the sketch, the code and the whole delivery come from one pair of hands. One person, no hand-offs, no telephone game.
Currently taking on new work · iOS · macOS · Web
Small enough to move fast. Experienced enough that the boring parts (signing, review, migrations, hand-over) do not blow up three weeks before launch.
iOS, iPadOS, macOS and the web. Concept, interface, data model, backend and the shipped binary. One head holding the whole picture.
Certificates, provisioning, hardened runtime, notarisation, store metadata, review notes. The part that quietly eats a launch, handled.
Apple's on-device models where they genuinely help. No server, no subscription, no user text leaving the machine. See WaitingFor.
Legacy modernisation, a project that lost its way, an inherited codebase nobody dares touch. Twenty years of that is the day job.
Not case studies for a client, but products I own, run and support. Which is the honest way to show what a build here looks like.
A companion for multi-day driving tours: the day's route, the fuel and lunch stops, the evening hotel. Organisers compose the tour, import GPX, and every driver's app updates the moment it is published.
A menu-bar app and Apple Mail extension that turns the messages you are owed a reply to into reminders and checks them off by itself when the answer arrives. Apple Intelligence spots the ones you forgot to mark, entirely on your own Mac.
Big programmes taught me what slows software down: hand-offs, waiting, and specifications nobody reads. So the loop here is short on purpose.
A call, then a written brief you can actually check against: what it is, what it is not, and what would make it a bad idea.
A working build in days, not a slide deck in weeks. Opinions about screens you can touch are worth far more than opinions about mockups.
Small releases, each one usable. You see progress every week and can change your mind while changing it is still cheap.
Source, build instructions, signing setup and the reasoning behind the design decisions. Or I stay on and keep running it. Your call.
I started as a software developer and spent two decades at IBM growing into the roles that decide whether large software actually lands: business design, programme management, delivery leadership across Vienna, Romania, India and China.
Paddockware is where I put that experience behind my own keyboard again, building complete products for people who would rather deal with one accountable engineer than a delivery pyramid.
Technical University of Vienna. Certified Scrum Master.
Application Management Services Austria; head of business analysis and design.
Insurance core platforms, hybrid cloud, logistics, run across four countries.
Responsible for a delivery portfolio of more than €800 million a year.
A €100 million-a-year platform implementation, from bid to running service.
Replacing the systems a business runs on, without stopping the business.
Built the practice and the career paths for a team of 100+.
200 people keeping other people's software alive.
Where it started, and where, with Paddockware, it is back.
Tell me what it should do and who it is for. If it is not a good fit you will hear that too. Quickly, and with a reason.