Hey Dev.to community! 👋
If you’ve been following my posts, you already know the constraints I work with: I’m 12 years old, I don’t have a $3,000 MacBook Pro, and I don’t have VC funding.
I build everything on a $150 Android phone using acode, treb edit, and pure, unfiltered stubbornness. 📱🔋
Over the last few months, this community has watched me navigate some wild, real-world challenges. We’ve built some actual things together, and I’ve learned more from this platform than any classroom could teach me:
🏆 The Receipts:
• The 24-Hour Holding Company: I asked for a co-founder on here, and 24 hours later, we launched a tech holding company to manage our projects. 🤝
• The Hosting Wars: Just recently, I woke up to find my app caught in the crossfire of two aggressive hosting providers trying to shut me down. Instead of panicking, I dug into the server logs, migrated the architecture on the fly, and my app survived both. That morning taught me more about resilience and DevOps than any tutorial ever could. 🛡️
• The Developer Social Network: I built a social network specifically for developers (and yes, adults are not allowed. Close the tab. 🚫👔).
• The Global Code Jam: I ran a global coding event and mapped out the exact Supabase architecture that held the real-time data together without crashing. 🌍
Through all of that chaos, my main focus has remained on one core project: KODA. 🤖✨
🧠 The Problem with Modern AI Tools
I built KODA entirely on this $150 phone because I was personally experiencing the pain of modern AI tools.
I was tired of AI wrappers that eat up all my RAM, drain my battery in 20 minutes, and force me to wait for massive JavaScript frameworks to load just to ask a simple coding question. 🪫
I wanted a tool that helps beginners learn HTML, CSS, and JavaScript instantly, without the bloat. Just pure, constraint-driven, lightweight code that respects the user's hardware and time. 💻
🚀 Where I Am Now
The core architecture is live. Supabase is handling the backend securely. The AI inference is optimized.
Most importantly, I have my "Founding 23" — 23 real, active users who have been testing it and giving me incredible, honest, and sometimes brutal feedback. I am so grateful for every single one of them. 🙏
But I know I have blind spots. I am 12, and I am building this in my bedroom. I need more eyes, more diverse use cases, and more senior perspectives to make this tool truly great. 👀
🎯 The Challenge: I Need 20 of You
I am on a mission to get KODA to its first 100 active users. To get there, I need 20 more developers from this community to actually use it.
I am not asking for your money. 💸
I am not asking for a long-term commitment or a newsletter subscription. ⏳
I am asking for 5 minutes of your time to try it, break it, and tell me the absolute truth. 🔨
👉 https://koda-aicodementor.netlify.app/
🛠️ How to Test It (The 5-Mute Gauntlet)
- Click the link. Notice how fast it loads. ⚡
- Ask it to explain a coding concept or paste a snippet to debug. 🧠
- Try to break the UI or confuse the AI with edge cases.
- See how it feels on your specific machine and browser.
💬 The Feedback Loop
If you try it, please drop a comment below and let me know:
✅ The Good: Did it load fast? Was the AI actually helpful and accurate?
⚠️ The Bad: Where did the UX fail you? Did the AI give generic, unhelpful answers?
🔥 The Ugly: What architectural decision would you change if you were the CTO of this project?
Building on a $150 phone teaches you how to survive hardware constraints. But building with this community teaches you how to build software for the real world. 🌍
I read every single comment. I will reply to every piece of feedback, good or bad. Let’s make this thing bulletproof together! 🚀🐯
Top comments (12)
Since it's mobile first, I'd fix this issue with the navbar:
ah, i see it now! the header is overlapping with the mobile browser's address bar. that's a classic viewport safe-area issue — thanks for circling it so clearly! 🙏
i've already written the css fix (adding
position: sticky,top: 0, andpadding-top: env(safe-area-inset-top)to respect the device's safe area).however, i'm currently out of netlify build minutes, so i'm batching this fix into my next deploy to keep things zero-bloat and cost-effective! i'll drop a reply here as soon as it's live so you can verify it.
to answer your other question: i code entirely on the phone using acode or trebedit. i don't use termux for this project. trebedit is lightweight enough to maintain that strict 142kb constraint without thermal throttling my $150 phone.
what device/browser are you testing on? i want to make sure this fix works perfectly for your exact setup when it goes live. 🐯📱
effessdev, thank you so much for catching this! this is exactly the kind of mobile-first feedback i was asking for in the post. 🙏
i'm opening my editor right now to fix that navbar issue. did it break on a specific viewport width, or was it a general flexbox/z-index overlap?
i really appreciate you taking the time to test it and report back. this is how we make it bulletproof! 🛠️📱
Thanks 😊 But didn't you notice that in your phone while testing? You code entirely on the phone, right? So you should've seen it? Or is it just my phone?
By the way, is it Acode or Codespaces this time? Just curious
you are totally right, i should have caught it! but honestly, when you stare at the same ui for 72 hours, you get "banner blindness" to your own bugs. plus, different android browsers handle css flexbox and z-index slightly differently, so your specific setup caught an edge case i missed. thank you for being my extra set of eyes! 👀
to answer your question: i code entirely on the phone using acode or trebedit. i don't use heavy linux environments like termux for this project. trebedit is incredibly lightweight and perfect for maintaining that strict 142kb, zero-bloat constraint without thermal throttling my $150 phone.
out of curiosity, what phone model and browser are you using? i want to make sure the navbar fix works perfectly for your exact setup. 🐯📱
Yeah that's correct 😅 Sometimes bugs never show up until somebody else tests the app. @akhourianmolkumar you also didn't notice the window opening at random positions first right? See these kinds of bugs are completely normal.
you are totally right! fresh eyes are the absolute best debugging tool. it's so easy to get "banner blindness" when you've been staring at the same code for days.
and great catch on the random window position bug too! 😅 i'm adding that to the fix list right alongside the navbar safe-area issue. having thorough testers like you and @akhourianmolkumar is exactly what makes this community so valuable.
i'm batching these css fixes into my next deploy (gotta save those netlify build minutes!), and i'll drop a note here as soon as they're live so you can verify. thanks again for being such an awesome early tester! 🐯📱
But the random window position bug was with ATLOCK, not KODA. 😅 I was saying that to @akhourianmolkumar
he misunderstood.
haha, oh my goodness, i completely misread that! 😅
thank goodness the random window position bug is on atlock and not koda. that makes me feel infinitely better about my code.
i will still squash that navbar safe-area issue for koda though! thanks for keeping me on my toes, and glad akhouri stepped in to clear up the misunderstanding. this is exactly why community testing is so valuable. 🐯📱
yeahh