Reflection on Rooots App Development
Current Dilemma and Reflections
I’m currently feeling quite lost after a conversation with Roland, where we reflected on our ikigai, goals, and plans for the next year. While I had a vision, my next steps are still unclear. I want to launch my app, “Roots,” and get users to use it. However, I’m plagued by doubts about its potential success. It’s essentially a to-do list app focused on social connections, but it doesn’t offer the full functionality of existing to-do list apps. Users might need an additional specific need to switch to or use “Roots” alongside their primary app.
These doubts highlight a potential flaw in my current plan, as I’ve spent perhaps too much time on the app—around 400 hours. I realize I should have sought early validation but can’t reclaim that time now. Dropping the app feels like repeating history with my previous app, SnipTube, which only attracted a few users before stagnating. I also risk falling into the same pattern with my third app, Orbit.
Potential Paths Forward
One possible solution is to move away from app development and focus more on content creation and community building. This aligns with advice from my friend Ali, who suggested I could spread my purpose through community rather than apps. I enjoy creating YouTube content, though video editing doesn’t provide much enjoyment, leading to infrequent uploads. However, considering my current position, it might be instrumental in achieving broader goals.
The app has been stagnant at about 99% completion for over six months, without tangible returns in terms of employment or app success—be that users or revenue. To change this trajectory, I could release the app via a private beta, ensuring gradual and controlled exposure rather than a full launch. Balancing this with my other commitments complicates the decision. I’m alone in this journey, creating a sense of uncertainty about the optimal direction.
Strengths and Differentiation
Despite the challenges, the app’s strengths include ease of storing and adding information. However, the redundancy emerges from apps like Notion, which allow users to build custom storage solutions. This realization prompts me to consider differentiation by integrating features like maintaining conversation topics tied to specific contacts. Such a blend could transform the app into a productive tool during personal interactions by connecting pre-stored questions or topics to individuals or groups.
Additionally, transitioning “Roots” to a B2B application could invite a CRM-like approach, targeting businesses with a focus on user interactions. Perhaps, I’m on the right path, needing only patience and more time to see the project reach fruition. Conversations and feedback have been pivotal, albeit abundant. I’ve pitched the concept widely, and the current challenge is ensuring that continued dialogue truly adds value to my efforts.
This reflection encapsulates my internal battle between doubt and perseverance as I navigate the uncertainties of app development and broader entrepreneurial endeavours. Whether to pivot or persist remains a complex decision that will require thoughtful consideration and strategic planning.