Indie app launch lessons from PediaPal and Auralog
This guide draws on a Launched podcast conversation between host Charlie Chapman and developer Adrian Eves, who moved from Apple’s accessibility team to building apps rooted in his own life. Eves did not start with a market map. He started with a messy shared note about his child’s health and a migraine that made logging feel impossible. Those two frustrations became PediaPal and Auralog. The repeatable decisions behind those launches are worth separating out: choosing a problem you already live with, designing for the worst moment of use, and treating community as part of the build rather than a marketing afterthought.
From personal friction to a first app
Adrian Eves had spent years saying he would ship an app. The push came after a layoff from Disney, when Paul Hudson advised him to build an indie app so he would always have something to fall back on. The problem he chose was close to home: shared Apple Notes about his child’s health had become unreliable. In the conversation he gives a concrete example — a note recording his three-year-old at 11 inches, an old measurement mixed in with current ones. That frustration became PediaPal, a health hub for kids.
The lesson is not that every developer needs a dramatic trigger. It is that a problem you already understand deeply gives you a head start on requirements, edge cases, and the language real users use. Before writing code, write down the specific moment the current workaround fails. For Eves, it was opening a note and not being able to tell which number was current.
What a month-long build challenge actually tests
After the emotional rollercoaster of launching PediaPal — and the letdown of not getting featured by Apple after a major Liquid Glass redesign — Eves found a different kind of motivation, which he describes as spite-driven development. A friend bet he could not release a second app within a month. The stakes, as he tells it, were ice cream. The result was Auralog, built around his own experience of chronic, debilitating migraines.
The constraint shaped the product. Auralog’s core interaction is a large “Save Now, Log Later” button, designed for a moment when the user is in pain and cannot navigate a detailed form. That is a useful pattern for any app with a high-friction moment: separate capture from classification. Let the user record the event first, then add context when they are able.
A one-month deadline is not a guarantee of quality. It is a forcing function for scope. The test is whether the core job still works when the deadline arrives. According to the account, Auralog quickly found traction and became Eves’s first project to generate meaningful, growing revenue.
Community as part of the build
Eves’s work extends beyond his own apps. He has helped run iOS Dev Happy Hour and co-founded CommunityKit, which the episode describes as the unofficial “glue” of WWDC week. He is also building Swift Sonic, his own conference — a music-festival-inspired event that pairs veteran “headliner” speakers with first-time “opener” speakers.
His motivation is pay-forward rather than promotion. As he puts it, the community has given him so much that it would not be right to behave like a dragon hoarding gold. For an indie developer, that framing points to a practical move: participate before you need something. Answer questions, share what you are learning, and show up consistently. That is different from treating a community as a distribution channel.
A short checklist before you ship
- Name the exact workaround your app replaces, not just the category it belongs to.
- Identify the worst moment a user will open the app and design the first screen for that moment.
- Separate capture from classification so a user can record first and organize later.
- Decide what a deadline will force you to cut, and confirm the core job survives the cut.
- Join one community where your users or peers already gather, and contribute before you ask for attention.
- Treat a feature rejection as feedback on distribution, not a verdict on the product.
Frequently asked questions
What is PediaPal?
PediaPal is a health hub for kids that Adrian Eves built after struggling to track his child’s health data across shared Apple Notes. It was his first indie app.
What is Auralog?
Auralog is a migraine tracking app built around Eves’s own experience with chronic migraines. Its core feature is a large “Save Now, Log Later” button designed for use during a painful episode.
What does “spite-driven development” mean here?
In this context it refers to using frustration or a friendly challenge as motivation to ship. Eves built Auralog after a friend bet he could not release an app within a month.
Did PediaPal get featured by Apple?
According to the account, PediaPal did not get an Apple feature after a major Liquid Glass redesign. That outcome became part of the motivation for the next project rather than the end of the story.