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
Software that keeps working when the network doesn't.
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.
What we do
Engagements range from a single application to the platform, pipeline and operational work around it. The list below is what we take on directly.
Web platforms
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.
Cloud & infrastructure
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.
Data & integration
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 & compliance engineering
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.
Maintenance & support
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.
Our products
Products we build and support ourselves. They are where our engineering standards are visible without a contract in the way.
iPhone · in preparation for App Store release
Route Foundry
Create the route. Own the file.
A local-first route planner 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. Free for 21 days, then $4.99 once. No subscription.
- Plan by tapping the map or drawing freehand; numbered points you can reorder by dragging, routed by Apple Directions, an offline routing pack, or a straight line.
- Elevation profiles calculated on the device from open terrain data — your route is never uploaded anywhere.
- Import and export GPX, TCX Course, KML, FIT Course and a lossless native project format.
- Offline maps from raster MBTiles files you already have — the app never downloads tiles on your behalf.
- Platform
- iPhone
- Requires
- iOS 18 or later
- Account
- None
- Data collected
- None
- Works offline
- Yes
- Status
- Pre-release
iPhone · iPad · Apple Watch · preparing for App Store release
GymLogger
Train. Track. Progress.
A private, local-first strength training log with fast set entry, routines, programs, progression guidance, Apple Health context and a real Watch workflow. No GymLogger account, advertising or subscription.
- Full-featured 30-day trial, then one Lifetime Unlock capped at US $9.99.
- StoreKit ties the trial and purchase to the App Store account, so reinstalling does not restart the trial.
- Optional private iCloud mirroring for non-health training data; Health-derived summaries stay local.
- Workout history, personal records, charts, comparison, import and clearly scoped exports.
- Platforms
- iPhone, iPad, Apple Watch
- Requires
- iOS 18 / watchOS 11
- Account
- No GymLogger account
- Price
- 30 days free; ≤ US $9.99 once
- Health data
- Local only
- Status
- Pre-release
How we work
Three commitments that shape every engagement, because they are the ones most often skipped.
Claims you can check
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.
Failure paths are the feature
No network, denied permission, a corrupt file, a force-quit mid-write. We design for these first, because they are what users actually meet.
You own the output
Source, infrastructure definitions and documentation are yours at handover. Open formats over proprietary ones wherever a choice exists.
Have something to build?
Tell us what the software has to do and where it has to keep working.