r/theVibeCoding

This is the app (called "LWP+"), and I've shown here the video that I've published there:

https://play.google.com/store/apps/details?id=com.lb.lwp_plus

At first I was happy about what I created on the video, but then I thought that it looks more like a tutorial here, instead of maybe focusing on what's the most interesting. Surprisingly, ever since I've published the video, it actually got quite some views already (29 after 2 days), despite the fact it's a bit of a niche app. Still, I think maybe it can be improved.

I want to know what you guys think about the video (which has audio, BTW).

Here's about the app:

It's a live wallpaper app, that has these features:

1. Allows showing color/image/animation/video as content (users choose the file from the file system). No special effects so some users that complain about the dimming/zooming effects actually like using it. Users can also choose whether it should scroll or the type of automatic cropping.

2. Allows (some) control over the Material-You colors of the OS, as it lets users to choose the colors to report the OS about what's on the wallpaper. This means that like on Android 17, users can choose the colors they want (if the OS supports it) despite the content not matching it.

3. Setting of double-tap to lock the screen. Some launchers don't offer this, so I added it to the app too.

4. Some extra flags that (on some devices) should affect colors further, such as black/white text and/or black/white icons on status bar and/or lock screen and/or launcher.

The app is completely free, ad-based. Users can remove the ads including by just watching full screen ads. Originally it was created to offer dark-theme on devices as it wasn't a toggle on the OS settings, and was based on the colors of the wallpaper.

I feel vibe coding is becoming addictive

I’ll think:

“I need to go pee.”

Then immediately:

“Wait… let me give Claude one more task first.”

Same before making coffee. Same before eating. Sometimes before going to sleep.

It feels weirdly wrong to leave the coding agent sitting idle.

Short-form video gave us:

“one more reel.”

AI coding gave us:

“one more prompt.”

Anyone else doing this? 😅

I think I just need a safe place to share what I've been working on and why for the last few months.

I have been completely obsessed with vibe-coding this past year.

I have been programming since I was a child and have been fortunate enough to do it professionally for over a decade. I have always loved throwing my entire weight behind a project and stopping at absolutely nothing to solve the tough problems that present themselves during the process.

AI and vibe coding have accelerated that process for me tremendously; it has done so in such a way that I believe I have become even more obsessed with tackling deeper and deeper problems.

This acceleration has come at a cost though, and it's a cost I have only now begun to realize. As much as it feels like my agents are collaborating with me ... they are not. None of my ideas are being shared with anyone and I have become totally reclusive these last few months; almost afraid to share anything with anyone. I find myself spending more and more time testing out ideas, brainstorming more features, tracking down difficult bugs and totally ignoring the fact that I am doing this all in complete isolation for absolutely zero users. This is totally not how I used to work and something I feel I need to change.

Anyways; in order to help me break out of this rut ... I just want to post here what I've been working on; what the goals and thought processes were in creating each project. Each of these could be its own post, but I'm going to just get everything out that I can now and make individual posts later if it makes sense.

cook

cook is a build tool, a replacement for Make (and one day CMake) with a focus on top tier caching and supporting polyglot repos.

I care very deeply about infrastructure tools and I have always had a dream for building my own build tool. With AI and vibe coding I felt now was a great time to prototype some of the ideas I always wanted out of a build tool.

I had a great little prototype for cook built in about 10 days of vibe coding and decided I would take the project a bit more seriously. In hindsight, I really wish I had shown off what I had built then, it was cool and a fun little toy, but ... I wanted to "finish" it.

It didn't register to me that finishing cook meant: creating my own programming language, creating my own package manager, creating my own CAS caching system.

Now, Cook is all of those things and more.

I don't believe I have ever put more thought into a personal project than I have put into cook.

It can do some impressive things like build Doom 3. It's out of the toy category for sure and a tool I use now in all my other projects, but I would still say it's far from the enterprise tool I had set out to create initially.

These other two are projects I've made while I was working on cook. There are better alternatives out there for each of them; these did serve a niche problem I had, but I then got stuck building out features for users I did not have.

cliban

cliban was something I vibed out because I reached the ticket limit on the free tier of Linear. It is a kanban board and task manager completely in the terminal with a vim motion supporting tui. The killer feature for me was I could quickly grep for the task I was interested in and then open it and edit it in NeoVim.

It became apparent to me very early in the project that cliban was not just a great task manager, but also an amazing memory system for my agents and a way for me to orchestrate large complex tasks very easily.

I spent a lot of time making this kanban board agent first, and it is now my daily driver for all my agentic workflows.

However, I built this completely unaware that it was already created by Steve Yegge with his wonderful tool Beads.

I just recently became aware of Beads and reading through the README felt like a gut punch.

I was super excited to share cliban with people, and it feels like now there is little reason to.

The lesson keeps smacking me in the face: DO NOT BUILD IN ISOLATION.

For myself, there is little reason to switch to Beads over cliban. For someone starting fresh, though, I'd absolutely recommend looking at Beads and its established ecosystem before deciding which tool to use.

cliban will continue to be maintained as a great tool for me.

AyeAye

ayeaye is a small phone sized webapp and tmux session tracker that allows me to control my agents from my phone for vibing on the go.

If it wasn't so easy to create these tools nowadays I would have found that this too was already created in the form of ccmux before I started building this one out.

Mine is a bit different and catered to my tastes and my exact workflow and actually integrates with cliban, so I'm keeping it.

I just need to learn that "this is useful to me" does not mean "therefore I must spend a considerable amount of time making it perfect, and then I can convince others to use it".

"This is useful to me" needs to mean ... "make a post/video and share it as it is now".

I have learned a lot working with AI and vibe coding has honestly been a great experience.

When I was a kid learning how to code I would spend hours on problems and I relish those memories ... nothing in my adult life has really come close to that feeling of discovery and learning, but honestly working with AI and orchestrating agents has come damn near close.

It feels funny to say, but just as I had to mature as a programmer then I need to mature as one now. For me, maturing in this new world means sharing and collaborating with others as much as I humanly can.

Built a mobile idle game with Bevy 0.15 + egui. No sprites anywhere —

all visuals are procedural geometry drawn with egui's painter API.

Runs on Android and WASM.

You mine asteroids, automate a drone fleet, and receive transmissions

from something watching near the black hole.

One technical thing the Bevy community might find useful:

egui::Window click events are unreliable in bevy_egui 0.33. All

interactive UI uses painter + ui.interact() instead. Took a while

to land on that pattern but it's solid now.

Play in browser: https://rdug627.itch.io/voidrift

Source (MIT): https://github.com/rfd62794/VoidDrift

Prototype — more orbital rings and drone types in progress.

Mobile feedback especially welcome.