Architecture
Module boundaries, dependencies and layers of responsibility are decided explicitly, so a feature can be added, replaced or removed without destabilising the rest of the system.
A professional engineering team designing and developing modern digital software solutions for the iOS platform and related technologies — scalable, maintainable and built to stay reliable over time.
What the work consists of
Module boundaries, dependencies and layers of responsibility are decided explicitly, so a feature can be added, replaced or removed without destabilising the rest of the system.
Work is measured against the frame budget rather than impressions — 16.6 ms at 60 Hz, 8.3 ms at 120 Hz. Main-thread load, allocation pressure, cold-start time and energy impact are profiled on real devices.
Defensive state handling, predictable error paths and automated verification across the release pipeline. Reliability is designed in first and proven before anything reaches a device.
Interfaces follow platform conventions and accessibility standards: scalable type, contrast, motion preferences and assistive technology belong in the specification, not in an afterthought.
Readable code, documented decisions, consistent conventions and modular composition. Quality is measured by how the system reads to the engineer who opens it years later.
Deep work with the iOS platform and related technologies: concurrency models, data persistence, networking layers, background execution and the system frameworks these solutions are built upon.
The order the work is done in
Requirements become an architecture before production code exists: domain boundaries, data flow, state ownership and the failure cases the system has to survive.
Implementation follows that structure in small reviewable increments, with testing and static analysis running alongside development rather than after it.
Behaviour is profiled on real devices — rendering, memory, concurrency, startup, energy — and tuned against measured evidence instead of assumption.
Workflows, engineering standards and internal processes are reviewed continuously, so each project starts from a stronger baseline than the one before it.
What the practice is held to
New technologies and engineering approaches are explored deliberately, evaluated against real constraints, and adopted when they make systems measurably better.
Development processes are refined as carefully as the software itself: shorter feedback loops, automated checks and repeatable delivery.
Engineering standards follow the current state of the platform, so solutions stay compatible, supportable and ready for what the platform does next.
Decisions are judged by the cost they create years later — in maintenance, in onboarding, and in the ability to keep moving.
Technical excellence is a process, not a claim
Silkscreen marking · board revision 01ONOSTAS d.o.o.
Board rev 01 · Ljubljana, Slovenia