MyDiveLogs
A dive logbook for people who dive, built iPhone-first and honest about where your data lives.
- SwiftUI
- Swift 6
- Laravel 12
- MySQL
- WidgetKit
- ActivityKit
Custom software development · Lutz, Florida
Off-the-shelf systems make you bend your process to suit the software. We do it the other way round — the application is built around the way the work already gets done, and it keeps working after launch.
What we build
Most engagements start the same way: something important is being held together by a spreadsheet, a paper form, or somebody's memory.
The application your operation runs on — orders, jobs, inventory, billing. Built to match your process rather than a generic one, with the states and approvals your business actually uses.
Native apps in Swift and SwiftUI, built to work offline first and sync when there is signal — because the field is where the work happens and the signal usually isn't.
Making systems that were never designed to talk to each other do exactly that, and turning what comes back into the report somebody actually has to produce.
Software that runs a business is never finished. Maintenance, changes and the next version are part of the engagement, not a separate conversation you have to start.
Selected work
Four builds, four different shapes of problem — an operation's billing, a consumer app, sensors nobody could report on, and the paperwork behind every new starter.
A dive logbook for people who dive, built iPhone-first and honest about where your data lives.
Paper bills of lading replaced by a system that prices, approves, bills and reports on every load.
The paperwork for a new starter, produced correctly in about a minute instead of by hand each time.
Temperature sensors already on the network, turned into alerts that arrive in time and reports that arrive on their own.
How it goes
Most software that disappoints was never wrong technically — it was built before anyone had agreed what it was for.
Before anything is designed, we sit with the process as it runs today — including the spreadsheet nobody admits to and the step that only one person knows.
What it does, what it does not do, and what it costs — in plain language, before you commit. If the answer is that you do not need custom software, we will say so.
You see working software early and often, not a demo at the end. Changing your mind in week three is cheap; changing it after launch is not.
Going live is the middle of the project. Fixes, changes and the next version are expected, and the code is documented for whoever picks it up next — including if that is not us.
Who you would be working with
Lutz Computer Services is Patrick Brown — the person who scopes the work is the person who writes it and the person who answers the phone afterwards.
That is a deliberate limit on how much work runs at once, and it is the reason the systems above are still maintained years after they shipped. You will never be handed to an account manager, and nothing gets subcontracted to someone you have not met.
More about the practiceNext step
Describe the process that is costing you time. You will get a straight answer about whether custom software is worth it — including when it is not.
Start a project