I talked to a gentleman from ssa today. He informed me about a decision reversal. I assumed this was concerning my Federal case about ssa mishandling my case. He couldn't tell me much but said to wait 60 days for official correspondence. My lawyer has been pretty much silent other than confirming the reversal. My case is from Feb 2022.
Abstrakt Engine is a real-time audio-reactive visualizer. Point it at any sound, your music, the mic, whatever, and it wraps 3D geometry in painter textures and folds it into kaleidoscope mandalas that move with the audio. Runs natively at 120Hz, and you can record the result and export it as an MP4 to share. It's pure Kotlin + OpenGL ES, no engine, all the rendering is hand-rolled. Every frame is the actual app responding to audio in real time.
Play Store: https://play.google.com/store/apps/details?id=com.onojk.abstrakt
I started an add campain for my app. I selected a global audience. Would it have been better for me to target the US and Canada? Result: lots of installs but almost all from very low-CPI regions. Anything obvious I'm missing for getting quality installs instead of cheap ones ?Happy to share more detail. Thanks.
Spent tonight shipping abstrakt engine to Google Play, my first Android app, and it's the kind of thing I'm not sure I'd have finished solo without AI in the loop.
The whole thing was journal-driven: I'd describe what I wanted, let Claude Code handle implementation, then verify on-device (eyes-on-device was my only real source of truth for the visual stuff). Some of tonight's run:
The app itself is an audio-reactive 3D visualizer, feed it sound, get living geometry (cube symmetry, distortion, chromatic aberration, party mode, etc). It's actually the third stack of a trilogy I've built of the same idea: Python original, Rust desktop, now Android.
Biggest lesson reinforced tonight: "logs over guessing" beats intuition every time, even when your gut is sure it knows the bug.
It's live and free if anyone wants to poke at https://play.google.com/store/apps/details?id=com.onojk.abstrakt but mostly wanted to share the process, happy to talk through any of it.
It's done. After a bunch of late nights, abstrakt engine, is officially live on Google Play, worldwide. I mostly used Claude Code for the coding.
https://play.google.com/store/apps/details?id=com.onojk.abstrakt
This is stack #3:
It's an audio-reactive 3D visualizer , feed it sound and it turns it into living geometry. Cube geometry with 12-fold symmetry by default, plus a pile of effects you can mess with: distortion, chromatic aberration, lightning, color shaping, party mode, random mode, the works.
Tonight's launch run was a journey, keystore generation, signing config, real Play Billing, Crashlytics with an opt-out toggle, AdMob, a last-minute fix to random mode in live render, full pre-launch audit, then the worldwide rollout. Got it verified end to end before pushing the button.
Would love for you all to take it for a spin and tell me what you think, especially how the visuals react to different kinds of music. Feedback from this crowd means a lot since you've watched the whole thing come together.
Indie dev clearing Google's 12-tester / 14-day requirement.
What it is: abstrakt engine — a music visualizer that turns audio into reactive kaleidoscope visuals. Works with music playing on your device or live mic input. Free with ads, $2.99 Pro removes them. No accounts, no signup.
What I need: - 12 testers with Android devices - Stay opted in for 14 days (just keep it installed) - Open it at least once - Feedback welcome but not required How to join:
DM me the Gmail address tied to your Android device
I'll add you to the tester list and reply with the opt-in link
Open the opt-in link on your phone, tap "Become a tester"
Install from Play Store: https://play.google.com/store/apps/details?id=com.onojk.abstrakt
The app will show as "abstrakt engine (unreviewed)" until Google's review completes — that's normal. I'll reciprocate — drop your closed test in the comments and I'll join yours too.
I've spent the last several months building an audio-reactive symmetric visualizer in three different forms, mostly with Claude Code as the implementation hand. Same core idea each time — take an audio file, generate something visually compelling that responds to the music, fold it through a kaleidoscope, output video — but three completely different platforms and tech stacks.
**The trilogy:**
🐍 **abstrakt** — github.com/onojk/abstrakt — the original. Python + pygame visualizers piped through an FFmpeg kaleidoscope post-stack. Offline 4K pipeline. Lives at onojk123.com.
🦀 **abstrakt-deck** — github.com/onojk/abstrakt-deck — native Linux desktop app. Rust + wgpu + egui + cpal + symphonia. Real-time interactive, MIDI controllable, presets, the works.
📱 **abstrakt-engine** — github.com/onojk/abstrakt-engine — Android app currently approaching launch. Kotlin + Jetpack Compose + OpenGL ES 3.0. Audio file or live mic, MP4 export with audio muxed, 120Hz on a Galaxy S25.
**What vibecoding handled well:**
- Greenfield architecture decisions. Starting fresh in a new language/framework, AI is genuinely good at "set up the canonical structure for this." Saved me weeks per platform.
- Shader and signal processing math. Equirectangular projection, FFT band extraction, kaleidoscope fold geometry — stuff that's well-documented in academic and graphics literature.
- Plumbing. DataStore wiring, MediaCodec MP4 export, Compose state hoisting, ViewModel patterns. The boring tier that's 80% of what you actually write.
- Cross-platform porting. Once abstrakt-deck was working in Rust, porting features to abstrakt-engine (Kotlin) was much faster than building them fresh — the AI could read the Rust source and write the Kotlin equivalent, and I'd reason about the differences.
**What it didn't:**
- Visual quality. The AI cannot see what the visualizer looks like. "Looks good" is the human's job and there's no substitute for eyes-on testing with audio actually playing. I built a rule: code that compiles and passes tests ≠ feature works. Confirmed visually or it's not done.
- Multi-session memory. Across long projects, the AI doesn't remember what we built last week. I keep a journal in the repo (`notes/journal.md`) that the next session reads to catch up. This single habit changed productivity more than any prompting technique.
- Bug localization in big codebases. Once a project is 10k+ lines, "find the bug" becomes a real skill the AI struggles with. I've learned to bisect, add strategic Log.d, and narrow the problem MYSELF before asking for a fix. AI is great at applying a fix once the diagnosis is clear.
- Knowing when to stop. AI will happily ship a 5-slice marathon at 1AM with confidence. The "commit message says X is shipped" ≠ "X is actually committed" failure mode bit me twice. Now I always end with `git status` + `git log --oneline` + push verified.
**Some non-obvious lessons:**
- **The Compose-Popup-vs-ModalBottomSheet bug.** A dropdown menu that synchronously inflates 8+ items via WindowManager.addView on the UI thread can freeze for 2.7 seconds on a memory-tight device. Took a real debugging session to find. AI can write the fix, but only after a human helps narrow which file to look in.
- **GPL contamination is a real thing.** I wanted to port a Kdenlive filter's behavior. Read the algorithm, reimplemented from scratch in our own shader — keeps the engine MIT-clean. Worth being deliberate about.
- **Multiple AI windows touching the same repo = chaos.** Hit this when one window was editing files while another was being asked to read them. Pick a lane: AI is either your hands on the keyboard OR your sparring partner reading and reasoning. Not both simultaneously on the same code.
**Where this is going:** abstrakt-engine is approaching its first Play Store release. Crashlytics is being wired up now. After launch the rhythm will shift from "ship a slice a day" to "stricter quality gates per release." Pre-launch is a sprint; post-launch is a marathon.
Happy to answer questions about any of the three, the workflow, the Claude Code rhythm, or the journal-driven session pattern. Not a tutorial — just sharing what worked and what didn't across this trilogy.
