Four apps, built and shipped by me.

Most habit trackers lean on streak guilt and send personal data to a server. I wanted one that felt calm and kept everything on the phone.

Loam is published and earns downloads with no paid promotion. I am now improving its App Store listing and review count to grow that organic traffic.

The subscription architecture in Loam is the foundation for my Subscription and Paywall Setup offer, so you get a pattern already proven in a shipped app.

• A SwiftUI app on an MVVM structure, with SwiftData keeping habits and history on the device.
• On-device coaching with Core ML, so no habit data leaves the phone.
• HealthKit integration for habits that map to health data.
• A freemium model on StoreKit 2, with a paid tier already built and held until demand justifies releasing it.
• Adaptive layouts, so it works properly on iPad and not just as a scaled-up iPhone.

Planning meals and shopping are two separate chores, and people end up buying food they already own. The app joins them: what is in the pantry shapes what gets suggested.

Conversion was weaker than the product deserved, so I audited the listing and the campaigns. I caught and fixed a typo in the App Store screenshots, retargeted posts that were aimed at the wrong communities, and rebuilt seasonal campaigns around stronger hooks.

I treat the App Store page as part of the product. When I handle a submission or an MVP, I check the listing, screenshots and onboarding for the problems that quietly cost downloads.

• Meal recommendations driven by what the user has and likes.
• Barcode scanning to add items to the pantry in seconds.
• Pantry tracking that feeds the planner.
• App Store screenshots, listing copy and a seasonal campaign calendar, so launch work was part of the build and not an afterthought.

I built this after my dad passed away. While caring for my aging parents from California, I stayed informed through texts and phone calls while my sister handled most of the hands-on care. Important details lived in message threads and in people's heads. I wanted one shared place for them.

I wrote the go-to-market plan alongside the app: a 14-day social campaign with English and Spanish posts, a source-of-truth feature inventory so every claim in a post matches what the app does, and outreach to California aging organizations asking to be listed.

I can build for a sensitive audience, choose careful wording and plan the product launch. Both matter for apps in health-adjacent or family categories.

• A free tier for caring for one person, and a Plus tier for people looking after more than one recipient, such as both parents.
• A design that works for a long-distance caregiver as well as the person on site.
• A tone and feature set written with care: the app organizes information and does not make health claims.

I built Lading to help with my own upcoming move. Boxes get lost, nobody remembers what is in them, and there is no way to confirm everything made it onto the truck.

Lading is in beta on TestFlight, and I am collecting quick feedback from testers before the paid launch.

Lading shows how I go from a real need to a working beta fast, and how I scope a free tier and a paid unlock before building, so the business model is decided up front.

• Barcode and color-coded tracking, so every box has an identity you can scan.
• Photos tied to each box number, so contents are visible without opening anything.
• A truck load flow: check boxes on when loading and off when unloading, then reconcile the full inventory to see what is missing.
• A free tier sized for a studio move (one room, 20 boxes), with a one-time purchase planned for larger moves.