Devlog #04 – Rebuilt from scratch ʕ•ᴥ•ʔ

I scrapped the old UI, that I did with AI (yeah, should have not done that) entirely and rebuilt ReFlow with my own design. The previous version used colors suggested by Claude and honestly looked too generic. The reviewer was right about that.

The new design is actually mine.

I decided the river is gone. Instead there’s a weekly circle tracker, seven circles that fill as you stay clean. It’s simpler and more honest about what the app actually does.

The counter now shows days, hours, and minutes since your last slip, the Impulse button turns the whole screen green for 60 seconds with a breathing animation. The AI companion stayed mostly the same as it is just an API, it simply adapted to the new layout.

What was hard:

• I always struggle with designing new UI by myself because I think it is not good enough (maybe that is why I used Claude at first)

What was easy:

• the circle tracker logic.

What took way too long:

• getting the slip button to actually reset the counter.

This version is 100% my own work except for the AI companion which still uses DeepSeek. No AI-generated UI this time. If this still looks like AI to someone, I don’t know what to tell them ʕ•ᴥ•ʔ

Devlog #03 – Almost There 🤍

Hey everyone ʕ•ᴥ•ʔ

ReFlow is almost ready to ship. This project has been a journey – kinda more personal than anything else I’ve built on Stardance.

What came easily

The onboarding flow with localStorage fell into place quickly. Name your addiction, set your reason, and it just works. The SVG river with the dark background, algae, and fish was surprisingly smooth to build – I had a clear vision and the code followed. Deploying to Vercel and hiding the API key with environment variables went way smoother than I expected.

What fought me

The AI companion was a pain. First Gemini gave me CORS issues. Then OpenRouter rate-limited me instantly. Finally got DeepSeek working through a serverless function, but it took hours of debugging. The routing on Vercel also broke my links - pages kept redirecting to index.html until I renamed home.html to track.html.

Where it stands

The river is alive. The AI (surprisingly) listens without judgment. The timer ticks every second. You can name your addiction, track your days, and talk things through. Everything stores locally - no accounts, no tracking, no bullshit.

Shipping soon. A few more details to wrap up and ReFlow goes live.

Honestly, this one means more than Stardust. If it helps even one person feel less alone, it was worth every hour.

Hope you all like it 🤍

Devlog #02 – UI Overhaul & Progress

Hey everyone ʕ•ᴥ•ʔ

I completely redesigned the ReFlow UI today. The old beige version felt flat and didn’t match the calm atmosphere I wanted for an addiction recovery tool.

Claude helped brainstorm the new green and yellow color scheme – green for growth and healing, yellow for warmth. It works way better.

But I built the actual functionality myself. The Get Started button with localStorage checks, the addiction name and reason inputs, the confirmation dialog if you already have data saved - all my code. The canvas river skeleton is in place, and I spent time planning how to animate water levels smoothly.

Also got the AI companion working with DeepSeek’s free API after struggling with Gemini (CORS) and OpenRouter (rate limits). The companion has strict guardrails so it won’t judge, give medical advice, or say anything harmful.

Right now at about 3.5 hours. The river animation is the last big piece before shipping.

The AI API is not ready yet, just some static answers a user can get.

This project is personal. I know what addiction feels like, and I wanted to build something that doesn’t punish you for slipping – just shows you the river can always flow again 🤍

Rebuilt the entire project as a personal portfolio for the Personal Site mission.

Three pages:

• Home with about me and skills
• Projects with KeyGlow and ReFlow
• Contact with links. Simple, clean, no frameworks.

Ready for re-review ʕ•ᴥ•ʔ

Devlog #01 – The river begins 🤍

I started building ReFlow today.
It’s a minimalist addiction recovery tracker where your progress is visualized as a living river.
Stay clean, the river fills.
Slip, it gently recedes.
No guilt, no punishment.
Almost got the landing page structure done – navigation with the logo on the left, Home and Track buttons on the right.

The idea came from my own struggles. I wanted something that just shows you that the river can always flow again. Tomorrow I’ll start working on the river animation and the day counter.
Built with pure HTML and CSS for now. Forn now, no frameworks, no bloat. Keeping it simple.
I know 1h and 15 mins might seem a lot for just the page structure that I have done, but I was so indecisive about colors I ended up changing them a lot and time was ticking in the background ʕ•ᴥ•ʔ

KeyGlow is finally shipping 🤍

Hello everyone, I hope you are all doing great!

After a lot of coding, debugging, testing and polishing, KeyGlow is finally ready to be released.

This project started as a simple idea: create a fun keyboard statistics tool that allows people to understand their keyboard usage without becoming a keylogger.

The final development phase ʕ•ᴥ•ʔ

The last stage of development was focused mostly on polishing the project and preparing everything for release.

At this point, instead of adding more features, I decided to focus on reliability and making sure the existing features worked properly.

Some of the final improvements included:

• Fixing edge cases
• Improving database handling
• Adding corrupted JSON detection
• Adding invalid database format detection
• Adding save error handling
• Improving reset behavior
• Adding automatic folder creation
• Testing installation in clean environments

A big part of software development is not only creating new features, but making sure other people can actually use what you built.

Making KeyGlow feel complete ʕ•ᴥ•ʔ

During the final hours of development, I focused on improving the overall experience.

Some smaller additions made KeyGlow feel much more like a complete application:

• ASCII KeyGlow logo
• keyglow logo
• keyglow info
• keyglow joke
• Better CLI experience
• Improved documentation
• Installation demo
• Project screenshots

From a local project to a real package ʕ•ᴥ•ʔ

One of the biggest milestones was turning KeyGlow from a project running only on my machine into a real Python package.

The project went from:

“A tool that works only for me”

to:

pip install keyglow

And I am glad I managed to release it, as I have never done such thing before.

AI Usage ʕ•ᴥ•ʔ

I need to admit, that I used AI for this project, however, biggest part of it was done fully by myself.
I used AI to learn about Typer library commands, and tables from Richer library, I also used it a little bit to validate the process of monitoring the keys, all that to ensure the project is indeed safe to deploy.

Final Thoughts ʕ•ᴥ•ʔ

It is a small project built around a simple idea: showing people interesting statistics about something they use every single day - their keyboard.
But building it was a great experience.
The project went through the full process:

• Idea
• Development
• Testing
• Documentation
• Packaging
• Release

That’s quite a long devlog, isn’t it ʕ•ᴥ•ʔ
I really hope you will like it and review it positively 🤍

Hello everyone 🤍

I hope you’re all doing great!

Just a little development update on KeyGlow.

Over the past few days I’ve been working on polishing the project instead of constantly adding new features. My goal from the very beginning has been to make KeyGlow feel like a real, reliable CLI tool rather than just another weekend prototype.

For anyone who hasn’t seen it before, KeyGlow is a privacy-first keyboard usage analyzer. It generates keyboard usage statistics and a simple heatmap while never storing what you type. No typed text, no passwords, no key sequences - only anonymous key frequency counters stored locally on your own machine.

Since the last update, quite a lot has changed:

• I added real-time keyboard monitoring.
• I implemented automatic saving while monitoring.
• Added keyboard and mouse inactivity detection with configurable timeout.
• Added the ability to disable automatic shutdown when desired.
• Improved local storage by moving everything into a dedicated ~/KeyGlow/ directory.
• Added JSON, CSV and TXT export support.
• Added an information command displaying database size, stored keys, total presses and other useful details.
• Added confirmation before deleting collected data, along with a –force / -f option for power users.
• Improved error handling for corrupted databases and invalid data.
• Added automatic creation of missing storage/export directories.
• Cleaned up dozens of small edge cases and improved the overall stability of the application.
• Wrote a complete README and documentation.
• Added a completely unnecessary but absolutely essential keyglow joke command because every CLI deserves at least a little personality.

At this point, most of my work isn’t about adding new features anymore (though it is tempting not gonna lie)-it’s about making sure the tool behaves correctly in every situation. That means testing fresh installations, handling invalid input gracefully, making the CLI feel polished, and improving the overall user experience.

The project is now very close to its first public release.

Before I publish it, there are only a few things left to finish:

• Debug a few remaining pieces of code.
• Update the KeyGlow ASCII logo.
• Package everything properly.
• Publish the project on PyPI.

Once that’s done, anyone will be able to install it with a simple:
“pip install keyglow”
I’m genuinely excited to finally share this project. It started as a small idea and slowly grew into something that feels like a proper open-source tool. There’s still plenty of room for future improvements, but I’m really happy with where it is today.

Thank you to everyone following the development so far. I can’t wait to release KeyGlow and hear what people think! 🤍

Devlog #3
Hello there again, what’s up?

I managed to add KeyGlow inactivity detector 🤍

It basically detects whether you move your mouse or write anything with a keyboard, and if you don’t it disables keys monitoring.
I added custom timeout in minutes.

How cool is that ʕ•ᴥ•ʔ

Devlog #2
What’s up, I hope you all are doing great 🤍

Still working on my KeyGlow ʕ•ᴥ•ʔ
I want to perfect it as much as I can.
Recently, I added a privacy model, and inactivity detector which I will talk about in the next devlog!

Here are some difficulties that I encountered:

• Mouse inactivity tracking, that involved checking movement, scroll and clicks.
• Explaining clearly to everyone what is my “privacy model”

I did those things with ease:

• Writing new commands overall, I already learned how to do it fast and efficiently.

Stay tuned for more if you like CLI Tools like this one ʕ•ᴥ•ʔ

Subtle Foreshadowing 👀🤍

I just finished the basics of my CLI Tool.
Proud to say I did it mostly by myself ʕ•ᴥ•ʔ
This will probably be kind of epic after release, though I still need to work a lot.

Things I menaged to do easily:

• Reading data from file, loading it into a “buffer”
• Coloring TUI
• Making tables and ASCII Art (just needed to search for docs)

Things I struggled with so far:

• The core mechanic such as receiving data from keyboard
• Converting that data into something easy to work with and making it file-attachable, and also human readable.

We all love CLI, riiiiight?

Just finished second and third webpage for Stardance portfolio!

This is a simple, minimalist portfolio website
Built with pure HTML and CSS – no frameworks, no backend, just the basics.
Projects and Contact webpages!

Just finished building my first real webpage project for Stardance!

This is a simple, minimalist portfolio website, first site of 3 I want to do.
Built with pure HTML and CSS – no frameworks, no backend, just the basics.

What I learned:

• Structuring a responsive dual-panel layout with FlexboxForm validation with regex patterns for credit card fieldsCSS animations and hover effects
• Deploying to GitHub Pages for the first time
• Writing a proper README that actually helps people

What went wrong (and got fixed):

• Accidentally broke the entire deployment while trying to add a custom domainHad to disable and re-enable GitHub Pages to fix it