Halt Scanner
iOS app, my own productA real time trading halt alert app on the App Store, built, shipped and maintained by me. It is the reason I can tell you what App Store review will reject before you build it.
View on the App StoreApp Development
Hampton Design · Tampa, Florida
I build and run my own iOS app, which means client app work is not a first attempt. I have shipped through App Store review, run subscriptions, handled crash reports and answered real users.
Most requests are not a consumer app. They are a tool a business needs and cannot buy: a dashboard, a portal, an automation that replaces three spreadsheets.
What you get
- Native iOS apps, built, submitted and maintained through App Store review.
- Web applications and internal dashboards, usually Next.js on Vercel with Supabase or Postgres behind them.
- Client facing report dashboards that replace a monthly PDF nobody opens.
- Legacy app rescues, where a product was built years ago by a vendor who is gone and the database still holds the users.
- Subscriptions, auth, push notifications and the parts people forget until launch week.
Who it is for
- Founders with a product idea who need it built and shipped, not prototyped forever.
- Businesses who bought software that nearly fits and keep paying for the gap.
- Companies sitting on a dead app and a live user database.
- Agencies and consultancies who need a dashboard their clients will actually log into.
Work I can point at
OpenReply
AI productProduct site and build for an AI reply tool.
View siteAI MedConsult
Healthcare AI, via RosariumA lead report dashboard that replaced a monthly email summary, built alongside the acquisition landing pages and the GA4 measurement plan for the same client.
Read the case studyHow the engagement runs
01
Scope
We cut the idea down to the version that can ship. Almost every first scope has twice the features it needs for launch.
02
Prototype
You get something you can tap on inside the first week or two, running on a real URL or a TestFlight build.
03
Build
Weekly builds you can use. Bugs get fixed in the week they are found, not in a sprint review.
04
Ship and maintain
Store submission, release notes, crash monitoring and the fixes that follow. Launch is the start of the work, not the end.
Questions people ask
Do you build native apps or web apps?
Both. Native iOS when the product needs push notifications, offline use, or the App Store as a channel. A web application when it has to run everywhere and update instantly. If you are not sure, start with the web app.
Have you actually shipped something to the App Store?
Yes. Halt Scanner is my own app, live on the App Store, with real users and real reviews. I maintain it, which is a different skill from launching it.
Can you rescue an app a previous developer abandoned?
Often, yes. The question is whether the database and the accounts survived. If the user data is intact, a relaunch is usually cheaper than a rebuild, and the existing users are the whole asset.
What stack do you use?
Swift and SwiftUI for iOS. Next.js on Vercel with Postgres or Supabase for web applications. Stripe for payments. I pick boring, well documented tools so the next developer can read the code.
Will I own the code?
Yes. The repository is in your name or your company's from the first commit.
Related services
Let’s talk
Tell me what the app has to do and who has to use it. You get a scope and a number, not a discovery phase.