Introduction
Hi everyone, I'm Gabry848, I'm 16 years old and I've been coding since I was 12. This is the story of how I built MyTaskly, a task manager controlled through AI voice chat, starting from scratch and reaching publication on the Google Play Store.
I want to share this journey not to brag, but because I believe that seeing the real process, with all the mistakes and pivots, can be useful to other developers. If you have advice or want to contribute, you're more than welcome.
Disclaimer: Everything you'll read really happened. The screenshots show the real evolution of the project.
The Starting Point
At the end of 2024 I wanted to create something concrete. After 4 years of programming, I had made many small projects but none that were truly complete and useful. Above all, I wanted to finally create something that my parents could actually use in daily life.
I was looking for a project that combined three elements:
- Real utility for non-technical people
- AI integration (I became super passionate about it since ChatGPT came out)
- Technical challenge big enough to make me grow
The idea came to me thinking about how my parents manage their commitments: post-it notes, voice memos, scattered to-do lists. What if they could simply talk to their phone and say 'remind me to call the doctor tomorrow at 3' without having to open apps, navigate menus, fill out forms?
That's how the concept of MyTaskly was born: an app where you manage everything through voice chat, as if you had a personal assistant.
Phase 1: Learning React Native (November 2024)
Before starting MyTaskly I needed to learn React Native. I already knew TypeScript from previous projects, but React Native was a new world.
Why React Native?
- Cross-platform (iOS and Android with a single codebase)
- Mature ecosystem
- I already knew TypeScript
The first month was... intense. React Native isn't exactly the simplest framework to start with. I created several small projects to get familiar: a calculator, a weather app, some experiments with animations.
During this period I was still attending high school (scientific lyceum with applied sciences) during normal hours. I was able to study quite quickly and dedicated the afternoon to programming, about 3-4 hours a day when possible.
Phase 2: The First Steps (January - March 2025)
In January 2025 I started the actual development of MyTaskly.
Initial Tech Stack
Backend:
- Python + FastAPI: I chose FastAPI after trying Django and Flask. FastAPI convinced me with its simplicity, speed and minimal setup, while remaining scalable. It was perfect for a project to manage alone.
- MySQL initially, then PostgreSQL: I made the switch for the more powerful triggers and events.
Frontend:
- React Native + Expo + TypeScript: Expo to start quickly, with the idea of ejecting later.
AI:
- OpenAI API (GPT-4): I chose the OpenAI ecosystem because it covers everything: chat, multimodal, TTS, STT (Whisper), image generation. Managing everything from a single platform is much more convenient when you're alone doing both frontend and backend.
The First UI Disaster
At the beginning I was developing using the browser preview (I had had problems with mobile setup). I had no idea what the interface should look like. The result?
Yes, it was ugly. Very ugly. But it worked, so I continued.
Phase 3: The Creative Crisis (February - May 2025)
In the following months I continued to develop, but something wasn't right. The app was becoming a normal todo list with a terrible interface. The AI was relegated to a separate chat screen, secondary.
The main problems:
- Inconsistent design: I tried UI kits, changed colors, nothing convinced me. The theme had gone from the first attempt to blue/dark, but remained chaotic.
- Marginal AI: The AI integration seemed like an addition, not the heart of the app.
- No clear identity: I no longer knew what I was building.
During this period I focused a lot on the backend. I developed the architecture, although I then completely restructured the file tree to make it more scalable.
I was frustrated. Every time I tried to modify something I realized I didn't have a clear concept in mind. My app was a disaster and I knew it.
I almost gave up.
Phase 4: The Turning Point (May 2025)
One day, by chance (I don't even remember how), I asked ChatGPT to generate an image of how I imagined the home page.
ChatGPT showed me a clean, minimal, black and white image that looked like a modern chatbot.
Boom.
It was exactly what I was looking for. Clean, minimal, focused on conversation. Not a todo list with chat, but a chat that manages your tasks.
From that moment I decided: I'm redoing the entire interface from scratch.
The Great Rewrite
I started using GitHub Copilot intensively and then Claude Code to accelerate development. This was the period with the most code written (you can clearly see it from the commits on GitHub).
An interesting pattern I noticed: as the project grew, my role evolved:
- Beginning: Writing most code manually, learning patterns and best practices
- Mid-project: Using AI tools (Copilot, Claude) for boilerplate and repetitive tasks, while I focused on architecture, complex logic, and integration between systems
- End of project: Coordinating all parts, making final technical decisions, ensuring everything works together seamlessly
Important clarification: AI tools accelerated development significantly, especially for UI components and CRUD operations. However, all architectural decisions, database design, API structure, authentication flow, WebSocket implementation, and AI integration logic were designed and implemented by me. The AI helped me code faster, not think less.
Some complex challenges I solved personally:
- Designing the database schema with triggers and events in PostgreSQL
- Implementing secure OAuth flow with Google
- Structuring the FastAPI backend for scalability
- Managing WebSocket connections for real-time features
- Integrating OpenAI's Whisper for voice chat with acceptable latency
- Debugging and fixing complex state management issues in React Native
The Result
This is MyTaskly's interface today, in December 2025. Clean, minimal, focused on chat. I'm really proud of it.
Note: more screen on MyTaskly repo
At first some screens were missing from the navigation (notes and calendar), which I added later.
Phase 5: Complex Features and Lessons Learned (June - December 2025)
Voice Chat: The Most Difficult Feature
Implementing voice chat was the biggest challenge. Currently I use Whisper (OpenAI's Speech-to-Text) with separate API calls to convert audio to text, then process the request and generate the response.
The problem? This implementation has a latency of about 2-3 seconds between sending the message and the start of the response. It's not bad, but it's not the fluid experience I'd like either.
The future solution: Once the separate MCP is completed, I'll be able to integrate OpenAI's real-time voice chat by connecting the MCP directly. This will allow much smoother and more natural conversations, with almost imperceptible latency.
It's one of the features I'm still actively working on.
The Internal MCP Mistake
A wrong technical choice I made: I implemented an internal MCP (Model Context Protocol) server, dependent on the main server. The MCP made direct database queries instead of using the server endpoints.
Why did I do it? It seemed simpler for the initial setup and easier to test.
What did I understand later? It's a terrible architectural choice. Every time I change the database or endpoints I have to test both the endpoints and the MCP. The code isn't scalable.
What am I doing now? I'm creating a separate MCP that communicates via API. I hope to complete it by the end of January 2026 and publish it. It will be MyTaskly's first official MCP and will make it easier to integrate MyTaskly into other AIs.
The Logo and Visual Identity
The logo also had a troubled evolution. Initially it had a blue theme that didn't convince me.
A friend of mine (whom I thank very much, he was the person I talked to most during development) made me several versions. One he had proposed seemed like a logo for a sandwich app... then almost by mistake I tried it in the app preview.
Wow. I loved it. I've kept it until now and I don't think I'll ever change it.
The website also had changes: initially I created it with v0 (when it had just been launched) with a blue and black theme, then I did the complete rebranding.
The Name: From Taskly to MyTaskly
Funny little note: initially it was called "Taskly". Then I discovered the name was already taken and the domain cost about 20,000 euros per year. I changed it to "MyTaskly" 😂
Numbers and Statistics
After almost a year of development:
- A substantial codebase managing frontend, backend, AI integration, authentication, real-time features, and complex state management across multiple screens and components
- Published in beta on Google Play Store
- Work hours: about 20-30 hours per week at the beginning, progressively increased
- Limited personal budget: invested my own savings in OpenAI API credits, Google Cloud services, and domain/hosting
- Technologies learned: React Native, Expo, FastAPI, PostgreSQL, Google Cloud, OAuth, WebSocket, OpenAI API, testing, complex project management
The Evening School Decision
In September 2025 I made an important choice: I switched from normal school (scientific lyceum with applied sciences) to evening school (technical institute), which starts at 6:40 PM.
Why? I wanted to have as much time as possible to dedicate to MyTaskly and my projects. I didn't lose any year, I simply changed path.
Note for international readers: In Italy, evening technical schools are a legitimate and officially recognized educational path, particularly designed for students who work or have other daytime commitments. It's not dropping out - you get the same diploma.
I'm very happy with the choice. Now I have entire days to develop, and in the evening I study what's needed.
What I Learned
Beyond technical skills, this project taught me a lot:
Technical Skills
- Managing a complex and large-scale project from scratch
- How to use AI tools effectively as productivity multipliers (they don't replace competence, they amplify it)
- React Native, Expo, FastAPI, PostgreSQL, Google Cloud at production level
- OAuth implementation, WebSocket real-time communication, testing strategies
- Separation of production and development databases
- Choice and management of libraries and dependencies
- Debugging complex issues across frontend and backend
Non-Technical Skills
- Persistence: Complex things take time. 11 months seems like a lot, but for a serious project it's normal.
- Decision making: When you're alone you have to make all the decisions. You'll make mistakes, but you'll learn.
- Project management: Moving from pure coder to project architect happened naturally as complexity grew.
- Marketing awareness: I discovered I find technical problem-solving more natural than marketing and user acquisition.
The Most Important Lesson
When you want something badly enough and you're willing to do whatever it takes, no one can stop you.
I was 15 when I started, no experience with React Native, limited budget, no team. Just the desire to create something useful.
Difficult things are interesting precisely because they're difficult. Everyone can do simple things. Difficult things are only done by those who don't give up.
The Future of MyTaskly
MyTaskly is now in beta on Google Play Store. It still needs to be released publicly, but the core is complete and working.
What's missing?
- Complete the separate MCP
- Optimize voice chat latency with real-time API integration
- Marketing and user acquisition strategy
- User feedback to understand what to improve
The Vision
I want MyTaskly to become the personal assistant everyone would like to have. Not an app where you enter tasks, but a natural conversation where you say what you need to do and the AI organizes everything for you.
Imagine saying: "I need to call the doctor, do the shopping, and remember my sister's birthday on Friday" and the app understands, organizes, reminds you at the right time.
This is MyTaskly.
Repository and Links
- Official website: mytasklyapp.com - Sign up for the waitlist to be among the first to try the app!
- GitHub: MyTaskly App (public frontend) - If you liked the project, a ⭐ on GitHub would fill me with joy!
- Backend: Will be published soon on my GitHub profile
- MCP Server: In development, publication expected for January 2026
If you find the project interesting and want to support it, signing up for the waitlist and leaving a star on GitHub would help me tremendously. Every small gesture counts when you're a single developer trying to make their work known! 🙏
Conclusions and Acknowledgments
This has been the biggest and most difficult project I've ever done. There were moments when I wanted to give up, moments of total frustration, but also moments of immense satisfaction when something finally worked.
A special thanks to my friend who helped me with the logo and with whom I discussed a lot during development. Having someone to compare notes with was fundamental.
If you made it this far, thanks for reading. If you have questions, advice, or want to contribute to the project, I'm more than open. I'm still learning and every feedback is precious.
For those who want to follow the development or try the app, you'll find everything on my GitHub.
And remember: big challenges make victories sweeter.
Gabry848
16 years old, developer, and determined to never give up.
Questions? Feedback?
Feel free to leave them in the comments! I'm here to learn and improve.
Some questions you can ask me:
- Technical details on specific implementations
- Advice on marketing and user acquisition
- Suggestions on features to add
- Similar experiences you've had
Thanks for reading! 🚀
Top comments (1)
This was really therapeutic to write! 😅
11 months of development had so many ups and downs. The hardest part wasn't the code - it was the moments of doubt when the UI looked terrible and I didn't know if I should continue.
To anyone reading this who's in the middle of a difficult project: keep going. The breakthrough moment will come.
What's your biggest challenge right now in your projects? Let's support each other! 💪