Mobile applications
Native iOS development in Swift and SwiftUI, from first prototype through App Store review and the releases after it. Offline-capable and local-first architectures a speciality.
Information technology solutions
Divith Technologies designs, builds and maintains software — mobile applications, web platforms, cloud infrastructure and the integrations between them. We build our own products to the same standard we build for clients.
Engagements range from a single application to the platform, pipeline and operational work around it. The list below is what we take on directly.
Native iOS development in Swift and SwiftUI, from first prototype through App Store review and the releases after it. Offline-capable and local-first architectures a speciality.
Web applications, internal tools and marketing sites — built to be fast on ordinary connections, accessible by default, and simple enough that the next person can maintain them.
Deployment, hosting, CI/CD, backups and monitoring. Environments that can be rebuilt from source rather than remembered, so a handover isn't a rescue operation.
Moving data between systems that were never designed to talk to each other: file formats, APIs, migrations and the validation that keeps a bad import from becoming a bad database.
Privacy manifests, data-flow documentation, GDPR and App Store requirements handled as engineering work — written down, checkable against the code, not asserted in a policy page.
Ongoing care for software already in production — dependency updates, OS migrations, defect triage and the unglamorous work that keeps an application shippable year after year.
Products we build and support ourselves. They are where our engineering standards are visible without a contract in the way.
Create the route. Own the file. Navigate offline.
A local-first route planner and navigator for hiking, walking, commuting, road cycling, gravel, MTB and motorcycle touring. No account, no backend, no cloud database — routes live on the device unless you export them.
Route Foundry is our first published product. Anything else we are working on will be listed here when it exists, not before.
Three commitments that shape every engagement, because they are the ones most often skipped.
If the software says your data stays on your device, there is a document naming every file it writes and every request it makes — and a test that fails if that stops being true.
No network, denied permission, a corrupt file, a force-quit mid-write. We design for these first, because they are what users actually meet.
Source, infrastructure definitions and documentation are yours at handover. Open formats over proprietary ones wherever a choice exists.
Tell us what the software has to do and where it has to keep working.