My Learnings as Indie App Developer: Building Identity Habits
Success in indie app development isn’t just about coding skills or marketing strategies—it’s about who you become as a developer. Drawing inspiration from James Clear’s concept of identity-based habits, I’ve identified ten key identities that have shaped my journey as an indie developer.
The Power of Identity-Based Habits
In “Atomic Habits”, James Clear emphasizes that the most effective way to change your habits is to focus on who you wish to become rather than what you want to achieve. As indie developers, this means building habits around the identity of being a professional, disciplined developer rather than just focusing on shipping features or making money.
Key Identity Habits for Indie Developers
1. I am a problem solver
The foundation of successful indie development lies in solving real problems. My journey as a problem solver began when I was planning a trip with friends and needed a way to split expenses evenly. Instead of searching for an existing solution, I saw an opportunity to create one. Starting with a basic MVP that could handle simple splits, I created an expense split app. Over time, as I understood user needs better, I expanded its capabilities.
2. I am a consistent shipper
Consistency in shipping updates has been a game-changer in my indie development journey. Rather than aiming for perfection, I’ve learned to embrace incremental progress. This regular shipping habit keeps me accountable and helps maintain momentum. Even if an update is small, like improving error messages or tweaking the UI, it contributes to the app’s evolution. This approach has helped me avoid the common trap of endless polishing and taught me that progress trumps perfection.
3. I am user-focused
Understanding and responding to user needs has become central to my development process. Instead of building features in isolation, I actively engage with my users through various channels. I’ve implemented an in-app feedback system that makes it easy for users to share their thoughts and report issues. This direct line of communication has been invaluable in shaping the direction of my apps and ensuring they truly serve their intended purpose.
4. I am a lifelong learner
The iOS development landscape is constantly evolving, and staying current is crucial for success. Expense Split app was initially built using UIkIt then it was upgraded to Swift UI. I have since upgraded it again to SwiftUI. Learning new technologies is a continuous learning process, and I am always seeking ways to expand my knowledge and stay ahead of the curve.
5. I am data-driven
As a developer, it’s tempting to add numerous features, but without understanding user behavior, it’s hard to know which ones truly matter. That’s why I always integrate analytics into my apps. This helps me track if a feature is being used—if not, I remove it. Analytics also provide insights into where users are coming from. For example, if I notice high impressions from a country but low conversions, it might indicate that my app isn’t ranking for the right keywords or that my App Store screenshots need localization. This data-driven approach ensures my efforts are aligned with user needs and helps me make informed decisions.
6. I am a Relatable Storyteller
I leverage storytelling and familiar references to create an emotional connection with users. In my expense-splitting app, I used characters from Friends—Ross, Rachel, Joey, and the gang—to make the screenshots more engaging and relatable. This approach resonated with users and made the app experience memorable. Stories build connection and trust, turning users into loyal fans.
7. I am a marketer
I used to think marketing wasn’t my job as a developer. As developers, we often overlook marketing. But driving traffic to your app is just as important as building it. But after seeing a 3-4x boost in impressions from tweaking my app’s title and keywords, I realized how crucial it is. Now, I spend 15 minutes daily on ASO—it’s a small habit with big results.
8. I am a Pro at Earning Ratings
Requesting ratings at the right moment has been a game-changer for boosting my app’s success. Instead of asking for ratings randomly or too frequently, I strategically time my prompts to align with user achievements—like successfully splitting a bill in my expense app. This proactive approach ensures that users see your app in the right context and are more likely to give it a rating. This also improves the App Store ranking of my app, which translates to more downloads and more revenue.
9. I am a confident monetizer
One of the main challenges Indie app developers face is a lack of confidence in their apps and the doubt: “Will anyone actually pay for this feature?” For years, I didn’t monetize my app for the same reason. But as an Indie developer, monetization isn’t just about making money—it’s also a way to validate your product’s value and test product-market fit.
When I finally added a paid feature, I was surprised to see users willing to pay for it. While it didn’t make me a fortune, it boosted my confidence and proved that my app was solving a problem worth paying for.
If you’re building apps as an Indie developer, don’t shy away from monetization—it’s the path to sustainability and growth.
10. I am a Celebrator
Celebrating small wins has become a vital part of my journey as an Indie app developer. Whether it’s shipping a new feature, reaching a milestone, or earning my first dollar from a paid feature, I’ve learned to pause and acknowledge the progress I’ve made.
This habit keeps me motivated and reinforces my identity as a developer who values both the journey and the destination. Every step forward, no matter how small, is worth celebrating.
Conclusion
These identity-based habits have transformed my approach to indie app development. They’ve helped me evolve from someone who just writes code to someone who builds sustainable, user-loved products. Remember, success in indie development isn’t just about technical skills—it’s about developing habits that align with the identity of a successful indie developer.
