Most new apps have two states. Empty and populated. If you’re lucky, there’s an error state too.
You see it in vibe-coded apps, and in a lot of apps new to the App Store. On day one it’s empty. Add some data and it’s populated. Come back three months later and it’s the same app with more rows.
That makes sense if you come from input and output systems. Something goes in, something comes out. The iPhone was never that kind of device.
Open the calculator and it isn’t a phone any more, it’s a calculator. Open Music and it’s an iPod. Watch a film and it’s a TV. That was the idea from the start, and it’s truer now than ever. When someone opens your app, the whole device is yours.
So you don’t need your obnoxious logo and brand name plastered all over it. They’ve already installed it and opened it. They know whose app it is.
What you should do with that device is let it change with them.
Any app that shows you things, or needs your data, should slowly evolve. It can learn your preferences. It can show you more insights. What you see on Day 100 shouldn’t be what you saw on Day 0.
Take a sleep app. A made-up one.
Day 0
How to use the app. That’s all you need today.
Day 30
How your first 30 days went, and a few tips.
Day 60
How you’re improving, with guidance and tips made for you.
Day 100
How much your sleep has improved. Your first 30 days next to your last 30.
One app, four different jobs.
Nobody needs Day 0 guidance on Day 100.
That change is what gives an app its value. It’s the reason your app isn’t a pamphlet, a static website or a PDF. Those say the same thing on the hundredth day as they did on the first. An app can change with you and your needs, and that’s what keeps people engaged and coming back.
If yours looks the same on Day 100 as it did on Day 0, you’ve built a very expensive pamphlet.