A Developer With No Laptop — Just a Phone and a Dream
I'm Arshad, a self-taught 18-year-old developer from Kudal, Maharashtra, India.
I have no laptop. Every single line of code, every bug fix, every deployment —
done entirely on Android. No excuses, just solutions.
Here are two real bug stories from my projects.
🐍 Project 1: Python Learner App
Live: https://python-learner--arshadansari786.replit.app/
GitHub: https://github.com/05unique-dotcom/python-learner-app
What is it?
A web-based Python learning platform for absolute beginners —
built with React, TypeScript, and Vite on Replit using AI assistance.
The Bugs 🐛
Bug #1 — Certificate Given Without Course Completion
The biggest embarrassment: users were receiving completion certificates
without finishing the course. The certificate logic wasn't checking
lesson completion status at all.
Fix: I identified that the certificate trigger had no validation gate.
After prompting the AI to add a completion check — the certificate now
only unlocks after every lesson is marked complete. Earned, not gifted.
Bug #2 — Dashboard Showing Lessons as Incomplete After Finishing
Even after a user finished a lesson, the dashboard still showed it as
incomplete. Progress tracking was broken.
Fix: The lesson state wasn't being saved properly to the database.
After debugging the state management logic, lessons now correctly
update and persist as "completed."
Bug #3 — Leaderboard Not Working
The leaderboard showed no data — it was completely non-functional.
Fix: The leaderboard data fetching logic had an error in how scores
were being read. After fixing the query, the leaderboard now displays
real user rankings properly.
🏎️ Project 2: Nitro Rush Revamped
Live: https://nitro-rush-revamped.lovable.app
GitHub: https://github.com/05unique-dotcom/nitro-rush-revamped
What is it?
A 3D browser racing game built with Three.js and WebGL —
playable directly in your mobile browser. No install needed.
The Bugs 🐛
Bug #1 — Only One Vehicle Available
Originally, players could only race with one car. No variety,
no choice, no fun.
Fix: Using AI-assisted prompting on Lovable, I expanded the
vehicle garage to include: Sports Car, Superbike, Rickshaw,
City Bus, Truck, and Hauler. Six vehicles. Each with a different feel.
Bug #2 — No Brakes! Vehicle Speed Couldn't Be Reduced
This was game-breaking. Players had Nitro boost and a joystick —
but zero braking ability. Once you speed up, you couldn't slow down.
Players kept crashing and losing. Unplayable at higher speeds.
Fix: I wrote a detailed prompt using ChatGPT first, then pasted it
into Lovable. It implemented a brake mechanic that gradually reduces
vehicle acceleration — giving players real speed control for the first time.
Bug #3 — Static, Repetitive Track
The same road environment repeated endlessly. No progression, no excitement.
Fix: Every 1000 meters, a new and different street environment
now loads — keeping the race feeling fresh and adventurous.
What I Learned
These weren't just code bugs — they were experience bugs.
A certificate that anyone could get meant nothing.
A racing game with no brakes wasn't a game at all.
Fixing bugs isn't just about making code work.
It's about making the experience work.
And yes — I did all of this on a phone. 📱
If you're a beginner reading this: your constraints don't define your limits.
Follow me on DEV: @05uniquedotcom
GitHub: github.com/05unique-dotcom
Top comments (0)