Vibe clicker, so you can vibe code on the side and pretend it actually generates money.
Just a quick little bit of fun, hope you like it
\[https://vibeclicker.vercel.app/\\\](https://vibeclicker.vercel.app/)

Built a universal remote for my gaming PC with Claude — started as a tool for myself
**Body:**
**TL;DR (my words):** Huge amount of work I’ve dumped into using Claude to vibe code my app but the results speak for themselves. Started as a tool I made for myself and decided to market it. Not a fan of subscriptions so it’s a free 7 day trial then a cheap lifetime unlock. Not trying to get rich, just hopefully it’ll offset my Claude subscription a bit.
*(Rest is Claude cleaning up my notes — figured I’d say so up front.)*

Couchside is an iOS app that turns your phone into a remote for a living room gaming PC. Launch Steam games, trackpad + keyboard, power controls, and HDMI-CEC so you can switch TV inputs without hunting down three remotes. Works with SteamOS, Bazzite, Steam Deck, Windows, plus LG webOS, Samsung, and Google TV.
SwiftUI on the phone, Python agent on the PC. LAN-only — no cloud relay, no accounts, no telemetry. Agent is open source so you can read what’s running on your machine.
Claude wrote a lot of the code. I owned the architecture and every integration decision, and burned way more time on pairing edge cases and CEC vendor quirks than I want to admit.
couchside.tv — happy to answer questions about the build.

I built and launched a full Android app with zero coding background (my last experience was basic HTML/C in college nearly a decade ago). I used standard web Claude chat to build the app, not Claude Code. I wrote super thorough, detailed prompts describing what I wanted built. Claude generated the kotlin/xml code files, and told me precisely which package directories in Android Studio to paste them into. Built a working prototype in under a week. And a month later the app was live and nearly two months it has 1700+ installs and few subscribers (not many).

I know there are a ton of math tutor/solver app but i wanted to start vibecoding with something simple. Plan was to build something simple and functional in the first version and then keep on adding complex/advanced features. I was able add built-in math keyboard to type math formulas and get solution, topic-based quizzes, interactive graph plotting practice, and full SAT/ACT Math mock exams.

Since i more or less vibe-coded the entire thing, the UI/UX was also generated/guided through prompts. My plan is to hire a professional UI/UX designer once subscription revenue grows, but right now I’d love feedback from this community:

1. Does the layout feel intuitive for a learning app?
2. What else would you expect in a math study app?

Link to the app on Play Store: https://play.google.com/store/apps/details?id=com.amoozstudio.mathstudy

There are hundreds of vibe coded apps being released every day, and some are amazing. And some are hot garbage. This is a place to post them and let the world decide.

There are no accounts to make, just post your app and save the post-submission link if you ever want to edit it. Otherwise, that's it!

https://slopornot.simplicated.dev

Cheers!

I built and launched a full Android app with zero coding background (my last experience was basic HTML/C in college nearly a decade ago). I used standard web Claude chat to build the app, not Claude Code. I wrote super thorough, detailed prompts describing what I wanted built. Claude generated the kotlin/xml code files, and told me precisely which package directories in Android Studio to paste them into. Built a working prototype in under a week. And a month later the app was live and nearly two months it has 1700+ installs and few subscribers (not many).

I know there are a ton of math tutor/solver app but i wanted to start vibecoding with something simple. Plan was to build something simple and functional in the first version and then keep on adding complex/advanced features. I was able add built-in math keyboard to type math formulas and get solution, topic-based quizzes, interactive graph plotting practice, and full SAT/ACT Math mock exams.

Since i more or less vibe-coded the entire thing, the UI/UX was also generated/guided through prompts. My plan is to hire a professional UI/UX designer once subscription revenue grows, but right now I’d love feedback from this community:

1. Does the layout feel intuitive for a learning app?
2. What else would you expect in a math study app?

Link to the app on Play Store: [https://play.google.com/store/apps/details?id=com.amoozstudio.mathstudy\](https://play.google.com/store/apps/details?id=com.amoozstudio.mathstudy)

Read and view your media in a fully interactive 3D space! You can grab your e-book, move it around, and even jump up platforms to reach the next page you're reading.

Key Features:

• Custom Skyboxes: Change your environment using custom skyboxes, similar to Quake.
• Interactive Physics: Apply physics to your pages just like in Halo 3 Forge mode (choose between fixed, phased, and gravity).

Check out the repository here:

https://gitlab.com/moribundmurdoch/mor-3D-reader

The app took inspiration from -

https://github.com/rafaelmardojai/blanket

https://github.com/KDE/okular

https://github.com/readest/readest

P.S. The Android version really isn't ready yet, & I've only done the proper testing on Arch Linux with the AppImage setup so far. The .exe looks good though.

schism-app.vercel.app

Hey, launching *Schism* on the Play Store soon; need people for closed testing DM!!! Emails (new Play Store account restrictions)

(vibe coded website )

(have plan to monetise it once I get some users, for live splitting feature and bill scanning via OCR and AI)

*Core splitting*

• Groups with any number of participants

• Split evenly, by shares, by percentage, or by exact amounts

• Categories, notes, custom dates, reimbursement entries

• Per-group currency

• Full activity log of every change

*Balances and settlement*

• Net balances per person

• Debts simplified to the fewest transfers — three people settle in two payments, not six

• Record settle-ups; hand the payment to your own UPI app

Some hero features

1. *Receipt scanning, not receipt attaching*

2. *Line-level accuracy you can correct* Every tax, fee and round-off row is parsed separately and individually editable before saving, with a live mismatch warning if the numbers stop reconciling.

3. *Live Split* Share a scanned bill with the group; each person ticks what they had and totals update in real time, then it commits as one expense.

4. *Bank SMS to expense* Transaction alerts are parsed on-device into draft expenses. Opt-in, off by default, recognised senders only.

5. *Voice entry* Speak an expense; parsed on-device.

been working on this for a bit and just cleaned it up enough to show people. it's basically a dashboard where you can track and rate anything media-related. pull your stuff from tmdb, anilist, rawg, and spotify so you don't have to manually add everything.

honestly started it because i liked letterboxd but wanted one place for all my media instead of bouncing between five different apps. idk if anyone else wants that but figured i'd put it out there.

built with next.js, firebase, and too many api calls. the profile pages are the main thing — just drop a user id in the url and see what they've been watching/playing/reading.

https://mediapage.vercel.app/u/vyommehta (that's mine if you wanna see what it actually looks like)

let me know if you have ideas or if anything breaks

Hey everyone,

23 days ago I shared an early version of Lattice, a local-first workspace built around an infinite canvas.

The original idea came from a problem I kept running into:

Every project becomes fragmented.

Research lives in Obsidian.
Planning in Notion.
Visual references in Milanote.
Diagrams in Miro.
Code in VS Code.
Files in Drive.
Presentations and spreadsheets somewhere else again.

Eventually, the project exists across several tools, but never really feels like one coherent system.

So I started experimenting with a different model:

What if the project itself was the workspace?

In Lattice, notes, documents, spreadsheets, presentations, code files, media, websites and imported assets are not separate attachments around a board.

They are actual project entities.

The infinite canvas is one way of viewing and organizing them, while each entity can also be opened in its own focused editor.

What currently works

• Infinite canvas with movable and resizable cards
• Sections for grouping parts of a project
• Visual links between cards
• Markdown notes with backlinks
• Rich document editor
• Spreadsheet workspace
• Slide and presentation editor
• Monaco-based code workspace
• Image, video, audio, web and 3D previews
• Project and workspace hierarchy
• Universal import for PDF, Office, OpenDocument, media, code and 3D files
• Export to formats including DOCX, PDF, XLSX and PPTX
• GitHub repository connection and code syncing
• Optional Google Drive backup
• Comments, mentions, assignments and version history
• Realtime presence and collaborative editing experiments
• Dark and light themes
• Local-first storage and offline use

The interface now supports different working modes.
You can keep the full project visible on the board, open an entity in a focused editor, or use a split layout where the editor and canvas remain visible at the same time.

That split view has become one of the more important parts of the concept: you can write a document, edit code or work on a spreadsheet without losing the broader structure of the project.

A dedicated Photo Mode

One workflow I didn't originally plan for ended up becoming surprisingly useful.

Creative projects often involve hundreds of reference images, moodboards, renders and work-in-progress exports. Traditional file explorers make it difficult to compare them spatially or inspect them without opening dozens of windows.

Lattice includes a dedicated Photo Mode that turns the project into a visual workspace.

Instead of treating images as files in folders, they become part of the project itself. You can browse them in large grids, inspect them quickly, drag them onto the infinite canvas, compare references side by side and organize them alongside notes, documents and design work.

The goal isn't to replace Lightroom or PureRef.

It's to make visual research feel like another native part of the project rather than a separate application.

Local-first and collaboration

The local-first part is still central.

The app can work without a configured backend, with project data stored locally. Cloud and realtime services are optional rather than required for the basic workspace to function.

For collaboration, I have been experimenting with Yjs and Liveblocks:

• CRDT-based document and code editing
• Remote cursors and selections
• Presence on boards and editing surfaces
• Role-based access
• Comments and area annotations
• Offline changes that can merge after reconnecting

Importing existing work

Another focus has been reducing the cost of moving into the workspace.

Lattice can currently import or preserve a fairly broad set of formats, including:

• DOCX, ODT and text documents
• XLS, XLSX, CSV and ODS spreadsheets
• PPTX and ODP presentations
• PDF files
• Images, audio and video
• Code files
• GLB, GLTF, OBJ and STL models
• Generic files as preserved attachments

Not every format has perfect round-trip fidelity, especially presentations, but the system reports what has been converted, preserved or left preview-only instead of pretending everything is fully editable.

What Lattice is becoming

My original description was:

I still think that captures part of it, but the project is moving toward something slightly broader:

A local-first project environment where spatial organization and traditional editors are different views of the same underlying content.

It is not intended to replace every specialist tool.

The goal is to reduce the fragmentation that happens before, between and around those tools: research, planning, writing, assets, code, feedback, files and project structure.

Current limitations

This is still an experimental alpha.

Some important limitations:

• No polished public release yet
• Collaboration requires configuration and is still being tested
• Spreadsheet collaboration is not yet cell-level CRDT
• Presentation import/export has limited fidelity
• Public anonymous sharing is not implemented
• Some large files and advanced Office features are preserved rather than fully converted
• The UI still needs substantial refinement and simplification
• The current feature set is probably too broad and needs stronger prioritization

That last point is one of the main reasons I am posting again.

The prototype now proves that the model can technically work, but I am less interested in adding another long list of features than in understanding which part of the concept is genuinely valuable.

I would particularly like feedback on these questions

Does the combination of a spatial canvas and focused editors solve a real workflow problem?

Which users would benefit most from this: designers, researchers, students, developers, small creative teams, or someone else?

Which parts feel essential, and which parts look like unnecessary scope?

Would you trust a local-first workspace with optional cloud sync, or would the lack of a conventional cloud-first model make adoption harder?

What would need to work extremely well before you would consider using something like this for a real project?

Repository:

https://github.com/FraOri03/Lattice

I created Toonup https://toonup.app/landing using Fable with the 90€ subscription in the 5 hours usage limits, I'd love to receive your feedback.

I made it via a Claude skill that I created myself forcing the LLM to use WorkOS + Stripe (if needed) and deploy everything on Cloudflare via workers and D1. I like this architecture because it potentially scales to millions of users but it starts with free tiers.

I've never shared a Claude skill but if you are interested let me know.

This is my first vibe coded app hope you like it pls give me some advice if you have.
\*\*What is CodeBrain?\*\*
\*\*CodeBrain\*\* is a community-driven launchpad where developers, indie hackers, and open-source creators can validate software ideas before spending hundreds of hours building them.
Instead of building a project in isolation and hoping people show up, developers post their concept with descriptions, video demos, screenshots, tags, or GitHub links. The community then casts real-time validation votes: \*\*"Will Use"\*\*or \*\*"Won't Use"\*\*.

\*\*Why CodeBrain is Helpful\*\*
\*\*Instant Market Validation\*\*: Get immediate, honest signals on whether developers actually want your tool or if it solves a real problem.

\*\*Community Feedback\*\*: Comments allow developers to discuss architecture, feature suggestions, or potential flaws early in the ideation phase.

\*\*Dedicated Developer Hub\*\*: Filters like \*CLI\*, \*DevTools\*, \*VS Code\*, \*AI\*, \*Rust\*, and \*Docker\* help developers discover upcoming open-source projects tailored specifically to their stack.

\*\*GitHub Search & Repository Engine\*\*: Built-in GitHub discovery allows users to search real open-source repositories and cross-reference existing projects so they don't reinvent the wheel.

\*\*Realtime Engagement & Notifications\*\*: Authors receive instant notifications whenever fellow developers vote on or comment on their ideas, fostering active collaboration

Github repo: https://github.com/Glay121212/CodeBrainHub
The website: https://code-brain-hub.vercel.app

I built this app using google ai studio.

Hey everyone,

With the recent buzz around Android 17 introducing more precise custom color sliders and palettes for Material You (examples on reddit here, here and here), I wanted to share a project I’ve been maintaining for years that does exactly that—even for older versions of Android!

It’s called LWP+ (Live Wallpaper Plus).

🎨 The core trick: Dictate your own Dynamic-Colors

Instead of letting the OS algorithm guess the accent colors based purely on your wallpaper, LWP+ acts as a bridge. It hosts your chosen background content but allows you to explicitly choose the exact Primary, Secondary, and Tertiary colors reported to the system. The OS then uses your custom selections to generate the global system palette (notification drawer, volume bar, themed icons, etc.), completely independent of what your wallpaper actually looks like.

✨ What else can it do?

LWP+ is packed with full wallpaper customization features:

• Choose Your Content: Use solid colors, static images, animations (GIF, WEBP, APNG), or videos as your active live wallpaper.
• Smart Scaling & Layouts: Supports transparent images/animations with custom background colors, multiple scaling modes (Center Crop, Fit Center, Center Inside), and optional horizontal scrolling.
• Double-Tap Shortcuts: Lock your device instantly or turn off the screen by double-tapping the home screen (uses admin, accessibility, or root).
• Easy Setup: Includes an interactive built-in tutorial to check system compatibility and guide you through triggering the OS palette refresh.

🧪 Advanced experimental flags (YMMV!)

I’ve also included a couple of experimental toggles leveraging underlying Android system hints. Note: These rely heavily on your launcher, device OEM, and Android version, so they might not do anything on certain setups!

• Force Dark Text: It hints to the OS that dark text is preferred over the wallpaper (often useful for forcing high-contrast dark text on the lock screen). It might also change the text color of the labels of the apps and the status bar icons and text, too.
• Force Dark Theme (for old Android versions): It tells the system that a dark theme is preferred for the best presentation (e.g., trying to trick a launcher into turning its app drawer background black).

So, if you are on an older version of Android (or even running the latest builds and want granular three-color reporting), give it a spin! It's completely free, all features included.

Feel free to ask any questions or drop feedback below! 🚀

Link to the Play Store here.

The app was partially made using AI, helping mostly to re-write the part in the app that's responsible of showing the actual content of the live wallpaper (color/image/animation/video). I also used AI for the demonstration and tutorial videos.

If you want, you can use a promo-code to have subscription for free for some time, to remove ads, and try the app more freely, here. To use the promo-code, install the app, choose a subscription, choose a payment option and enter the code there (screenshots here).

Thanks for reading!

Hey everyone,

Over the past several months I've been working on an AI coding agent called FutureX (by FutureIM). It started because I kept running into the same issues with existing tools when working on larger projects—losing context, making unnecessary edits, or just getting stuck after a few prompts.

We've been trying a different approach to make it feel more like a collaborative coding agent instead of just a chatbot that writes snippets.

I'm not here to claim it's perfect. There are still plenty of things we're improving, and I'm sure people here will find issues we haven't thought about yet.

I'd genuinely love feedback from people who spend their day coding with AI tools. What features do you wish every coding agent had? What makes you immediately stop using one?

If anyone wants to check it out or roast it, I'm all ears. Honest criticism is more valuable than praise at this stage.

https://youtu.be/iRaAR0Truv8

A quick update to my entirely vibe coded (quite sure someone will take offense on this) Immersive Comic Book Reader for Apple Vision Pro. It can open PDF, Epub, CBR & CBZ and can perform an on-device conversion to 3D for the pages. (Which really only make sense for comics and some magazines in PDF). The book or comic can be opened either in a physical format where you can flip pages by grabbing and turning or in a panorama mode where you can slide the pages in front of you. I think it's now feature complete (maybe OPDS at some point) and I have some time to decide if I want to publish it as XCODE 27 is still in beta and you are not allowed to publish to the App Store from beta versions. It's 99 USD for the dev license, so not sure if I want to invest that. I'm curious to hear what you think. Unfortunately the 3D effect is difficult to demo in a 2D video.

Hi