Don't download this app

In this video I share the emotional journey of launching my auto-captions app on the App Store... and why I'm asking people not to download it. After three months of development, countless late nights, and relentless optimization… I released I released the app with an issue. Watch as I navigate the tension between shipping software and maintaining personal quality standards Don't download this app: https://apps.apple.com/app/id6651823846 Follow my journey here: Website: https://adamlyttleapps.com Twitter: https://x.com/adamlyttleapps Github: https://github.com/adamlyttleapps Instagram: https://instagram.com/adamlyttleapps TikTok: https://tiktok.com/@adamlyttleapps Substack: https://adamlyttleapps.substack.com Apps by Adam Lyttle is the personal journey of an indie app developer, sharing valuable lessons and experiences to help fellow developers succeed in the competitive app market My channel is based on one simple premise: "A rising tide lifts all boats" — I share my experience, teach what I've learned and highlight the mistakes I've made along the way. Featured in this video: * Macbook Pro M3 with 34GB RAM & 1TB HDD * Macbook Pro M1 with 8GB RAM & 256GB HDD * Mouse: Logitech MX Master S3 * Keyboard: Logitech MX Keys * Microphone: Shure 7 * iPhone 15 Pro * iPhone 12 Mini * LEGO DUPLO: My First Duck 30327 As an indie app developer, there's a moment we all dread: when you realize your app isn't meeting your own standards. In my latest devlog entry, I'm sharing a raw, honest look at what happens when your app works beautifully... until it doesn't. The Journey So Far After three months of intense development with SwiftUI, I built an auto-caption generator for short-form content. The vision was clear: create an app that would make adding captions to videos effortless, all processed locally on device. No servers, no waiting, just smooth, efficient video processing. The core functionality worked perfectly: – Real-time caption generation – Dynamic text animations – Clean, intuitive interface – Local processing without external dependencies When Success Feels Like Failure Here's where things get interesting (and painful). During development, I tested with short clips - a six-second video of a duck. Everything seemed fine. The export process took about five to six seconds. Not ideal, but acceptable for development. Then came the reality check. I created a one-minute introduction video to announce the app's launch. When I hit export, my heart sank. The export time wasn't just slow - it was taking longer than the actual video duration to process. A three-minute video? That's over three minutes of export time. The bottleneck comes down to one crucial component: the H264 codec. While it's the standard format for web video (perfect for TikTok, YouTube Shorts, and Instagram Reels), it comes with a significant limitation. Each frame needs to be written to disk sequentially, creating a bottleneck that no amount of GPU optimization can overcome. Here's what's happening under the hood: – Frames render beautifully – Processing works efficiently – But writing to disk? That's where we hit the wall A simple test revealed the extent of the problem: Processing time without disk writing: 0.5 seconds Processing time with disk writing: 6-8 seconds The culprit: H264 codec's frame-by-frame writing process The Developer's Dilemma This is where the indie developer's journey gets personal. When your app is on the App Store, it's like having a billboard advertising your work to the world. Every download, every review, every user experience matters. I found myself in an uncomfortable position: my app was functional but not meeting my quality standards. Sure, I could argue that a one-minute export time for a one-minute video is "acceptable." But is it really? Does it deliver the experience I want my users to have? This experience highlights a crucial aspect of app development: knowing when to ship and when to hold back. While some feature cuts are acceptable (like aspect ratio controls being saved for a future update), core performance issues are different. It's not just about whether an app works - it's about whether it works in a way that makes you proud to put your name on it. The app is live on the App Store, but I'm already working on improvements. This isn't just about fixing a technical issue - it's about delivering on a promise of quality. For fellow developers working with SwiftUI and video processing, I'll be sharing my optimization journey and technical solutions in upcoming devlogs. Sometimes the best way to learn is through these challenges. #appdevelopment #devlog #codingvlog #apprelease