🛠️ Devlog 1 – Mr. Fortune
I started this project as a simple fortune-teller idea, but it quickly turned into a much larger experiment in state management and user flow.
My initial versions broke often — screens wouldn’t transition correctly, buttons wouldn’t respond, and features conflicted with each other. Instead of patching issues endlessly, I decided to restart from scratch and rebuild the app in a more structured way. This helped me understand the importance of planning flow before adding features.
One of the biggest challenges was managing multiple screens (user input, category selection, card choice, result, history, admin panel) using only vanilla JavaScript. I refactored the logic several times to avoid silent failures and ensure that every user action led to a clear next step.
I also implemented systems like daily usage limits, cooldowns, per-category limits, and a testing/admin mode. These features forced me to think about edge cases, persistence using local storage, and how to give users feedback when actions were blocked.
Most of my time was spent debugging and improving UX rather than writing new features. Small details like animations, transitions, and visual feedback made a big difference in how polished the project felt.
Overall, this project helped me learn how to:
structure a multi-screen web app without frameworks
manage application state reliably
debug UI and logic issues effectively
iterate on a project instead of abandoning it when things break
This was a challenging but rewarding project, and rebuilding it properly taught me more than trying to rush features.
