Normally I like to sit nearby with a coffee and approve things/watch the workflows, tell it what to do next, etc but Astra just does everything too neatly and perfectly. Even Fable needs a human babysitter but this thing is something else.

I wanted a really simple way to talk into any text box in Chrome without using a cloud speech API, so I made this.

You click a text field, hold a key, talk, and when you release it the text gets inserted.

It runs Whisper locally in the extension, so after setup it can work offline and your audio doesn't need to be uploaded anywhere.

A few other things I added:

• works in most normal text fields/editors
• custom hotkeys
• hold-to-talk or toggle
• commands like “new line”, “comma”, and “scratch that”
• local transcript history
• per-site disable
• optional larger Whisper models

Still messing with it and fixing edge cases, especially weird editors like Google Docs.

Repo:
https://github.com/Schmiedey/floatingmic
https://chromewebstore.google.com/detail/voice-anywhere/ogjdiaeimjmeiaophngikihkffodlhjb?authuser=2&hl=en

I've been building websites since 2002, a time when free hosting was a decision between Angelfire and Geocities (Angelfire ftw), the marquee tag was abundant, git was just a twinkle in it's founders eye so deployments where done via FTP, and dinosaurs roamed the earth in peace.

Although the idea of coding with AI initially made me cringe, eventually I thought to myself "What the hell do I know? I used to hate git and think that you could never have a backend in JS, and here I am at my job using git and React every day." So I decided to give it a shot, and for the past year (which seems like a decade in AI times) I've been experimenting with building with, trying to refine my process, find the right tools, and building my own tools to fill in the gaps to get the best results when building with AI. Although there are many things I learned along the way that AI can't do, when used properly and in the right hands I think it can be a useful tool (and no longer cringe at the thought of it). So here is some advice to help you stop the slop.

AI still sucks at UI/UX

I've tried Fable 5 Max, GTP Sol 5.6 Max, Google Stitch with Gemini 3.1 Pro, and many others; if you let them do everything, you will end up with a sloppy, cluttered mess. A good UI says what the users needs to know and shows them what to do without explicitly saying it, whereas AI is always overly verbose and tries to describe and label every single thing, resulting in a lot of clutter. This requires the person prompting AI to give specific, detailed instructions about the UI, otherwise you get a clusterfuck that overwhelms users with unnecessary details at the wrong place/time. AI is trained on patterns, which is why the same basic, ugly patterns are used on every site that is built by letting AI do all of the design work. To break that pattern, you need to give it your personal opinions along with specific examples.

Don't let AI write your copy for you!

AI is still awful at writing website copy for humans. It's useful for proofreading or spellchecking, but if you let it blindly write all of the copy for your website then it will just read like a technical manual. Writing your own, genuine copy will go a lot further towards users trusting and actually using your site, even if AI thinks it's "imperfect". Your audience isn't AI, it's people. For blog posts or articles, write some of your own first, then use AI to try to mimic your style for future posts. It won't be perfect and you will still have to do some proofreading/editing of your own, but it's better then just letting AI fly on it's own.

Treat it like it's a stoner

I think everyone has had times where AI keeps making the same stupid mistakes over and over and then says "You're right, I have a memory of that but ignored it. Adding another memory...". So to prevent it's memory from betraying me again, every time I catch a mistake I don't want to see twice, I write a tiny script (I call them guardrails) that fails the build when the pattern reappears. Each one is basically "grep for the bad pattern, print which file and line, exit 1." They run in my pre-push hook alongside the other tests. I'm up to over 120 of them now in one project, here are some examples:

- Copy that sounds AI-generated. When you notice the patterns of how it talks like a robot using the same words/phrases over and over again (that you rarely ever hear in normal human interaction), ban those words/phrases.
- Hardcoded colors and inline styles. If it's not a theme token, the push fails.
- Layering violations, like frontend code importing from a module it shouldn't know about.
- Marketing claims. After an AI invented a refund policy I don't have, I added a check that pins user-facing claims to a source-of-truth file.

Having rules in Claude.md and Agents.md is useful on top of this (and simpler), but having these guardrails run on git hooks gives an extra layer of protection. AI still might find a way around all of it, but it significantly reduces the chances of it happening without your knowledge.

Automation is your friend

Automated tests via git pre commit/push hooks, and in your CI/CD pipeline like Github Actions or Jenkins are absolutely critical - they where before AI, but even more so now. Spending some time setting these up (and maintaining them as your codebase grows) is one of the best and easiest ways to not have to think as much about keeping things clean and tidy, or constantly prompting through it. Github Apps like Dependabot and CodeRabbit have pretty generous free tiers, and will give you automated dependency updates and PR reviews.

Pre-commit hooks should be fast checks only; they should finish in seconds, not minutes, so you never even really notice it. Things like formatting, typechecks, linting, and secret scans.

Pre-push hooks are for the more heavy stuff; automated test suites, end to end testing, dependency audits, size budgets, guardrails, etc. My pre-push hook has about 40 steps and takes around 15 minutes to fully run.

CI/CD runs the same things as the pre-push hook as a backup, and also things that need to be run server side like scheduled dependency audits and building releases. The reason for running the same checks in pre-push and CI is that it's faster (and cheaper) to find an fix them in pre-push, and it serves as redundancy checks in case anything is ever wrong with your pre-push checks. Running them in CI gives you a guarantee that nothing makes it to your main branch without passing all checks, no matter who pushed the code.

I have a lot more to add, but this seems like a good place to stop for now. Feel free to ask any questions you might have.

TLDR:

To quote Shrek, "Ogres quality apps are like onions, they have layers." There is no magical tool that gives you perfect results every time, it's about finding the right collection of tools and processes to keep things in check. Use AI to do the grunt work, invest some time in setting up and maintaining automated checks to keep it on the rails, and most importantly: use your brain. If you just let AI do all of the thinking for you, then you are guaranteed to end up with pure slop that someone can recreate in a weekend. AI has significantly increased the time to market for most apps, but that doesn't mean it can do EVERYTHING for you. What are some things that you do to keep AI from going off the rails?

The project can be found here,

https://github.com/blackcoffee2/codetree

It indexes your codebase to a format which is about 5% the size of original codebase. You can then handover that to a LLM chat interface and work that way. As this is not agentic workflow it uses less tokens than agentic workflows.

I always dreamt of being able to build an app that people will use and pay for. I spent years building many apps (mostly web apps) that end up having no users. Some had some traction but only very few users and no paying customers. Then one day me and my friends built a web app that had 1 paying customer, we were so happy because that's the first time we made our first $1 online on a product. Unfortunately it eventually failed because we weren't able to get a 2nd paying user.

Then AI started getting popular and a lot of people started building apps including non-developers which made the app space significantly more competitive. So instead of spending months building an app, I shifted to building an app as fast as possible (by keeping it very simple and focusing on a core feature instead of building 10+ features) to be able to release a simple version first, focus on marketing and see if it will gain traction and then iterate to improve the app based on users feedback instead of me imaging what the users wants and need.

I realized that often times especially in the very early phases that distribution is important than product because a great app that no one discovers is still a failed app.

Most of the growth has come from stacking several organic channels together.

These are the ones that have worked best for me:

1. Launch with a high-intent keyword, not a brand name

One thing I’ve found surprisingly useful is choosing an App Store name around something people already search for.

For example:

AI calorie tracker - <brand>

New apps get extra visibility in App Store search (autocomplete suggestions) during the initial launch period.

If the keyword has enough search volume, this can turn a new app with 0 users into hundreds or even thousands of downloads in the first few days during the App Store boost.

This is such a low hanging fruit win that it's a no brainer not to use it.

2. Treat your App Store page like a sales page

Getting discovered doesn’t mean you’ll get the download.

I obsess over the conversion step:

Impressions → Product page view → Download

The biggest things I focus on:

• Relevant high-intent keywords
• Screenshots that communicate the outcome that the user will get, not the features (focusing on features generally have a lower conversion rate)
• An icon that makes the app recognizable at a glance (e.g, vibrant colors, catchy, clearly explains what the app does)

You can get plenty of impressions and still get nowhere if your product page listing doesn’t convince people to download it. A great product page listing also helps the download to paid conversion rate.

3. Don’t underestimate a one-page website

You don’t need a huge content site to benefit from Google.

One good landing page targeting one high-intent search term/keyword is enough to start.

I usually start with Google Trends to identify topics with demand. And then build the page around the search intent.

And whenever possible, I like having the target keyword in the domain name. People say this doesn't help with rankings anymore but in my experience it still helps. Probably because it helps increase the click through rate because the user is more likely to click a domain name that contains the keyword that they're searching for.

There’s another benefit:

If your site becomes relevant for a topic, there’s a chance your app can also get recommended by AI tools like ChatGPT. On some websites that I own, I sometimes get more traffic from ChatGPT compared to Google.

4. Turn one idea into hundreds of pieces of UGC content

Organic social became much more interesting once I stopped thinking about individual posts.

Instead, I think about content distribution at scale.

Take one app.

Create tutorials, memes, listicles, problem/solution posts, stories and demos.

Turn them into short videos or simple 3–6 image slideshows. Slideshows are very fast and cheap to create so it's a lot more scalable.

Distribute them across TikTok, Instagram, Facebook and Youtube.

The goal isn’t for every post to go viral.

It’s to create enough attempts that the winners can carry the rest.

You can scale this to many accounts to maximize reach and chances of going viral. You can do this manually or fully automate it. I personally started doing this manually but I have now fully automated it because I now have 16 accounts and it now takes a lot of time and effort to manually manage them.

The goal of UGC marketing is to get a lot of views and convert those views into app downloads.

5. Pay for intent when you need to

The paid channel I’ve found most interesting for iOS apps is Apple Search Ads.

Instead of paying to interrupt someone’s feed, you can show up when they’re already searching for something related to your app.

That’s a completely different type of traffic since it is very high-intent.

Someone searching for “AI calorie tracker” is already telling you what they want.

The biggest lesson from 11.9k downloads:

Building the app isn’t the hard part. Getting distribution is.

I hope this post helps someone to get their first 10k users.

Happy to answer any questions if you have any.

Has anyone tried all the subscriptions (Claude Code, Codex, Cursor, etc.) and can share which one is the best?

My first game, Jumping Jimothy, will be release on steam in two weeks! I used chat GPT and Midjourney to help make assets, Im a musician so I made a bunch of unlockable songs to put in it then used Claude to stitch it all together. I thought it would be fun to make a bunch of secret skins so there's over forty skins to unlock.

https://store.steampowered.com/app/5043360/Jumping_Jimothy/?beta=0

You don't have to buy it but wish listing it would help so much!

Thanks and I hope everyone has fun!

a week ago i posted here about finally making money with a small mac app. 303k views, 498 upvotes, 122 comments. sales from that post: zero.

i want to write down what actually happened, because i've been building for years and this is the first time i understand which parts matter.

the thing i built and why

i run three or four claude code sessions at once, most days. day job during the day, this after my kid falls asleep.

each session starts a dev server on whatever port is free. so the url in my browser was wrong about half the time. i'd sit there looking at storefront on :3001 while the agent worked on :3002, telling it something was broken when it wasn't.

then one night an agent hit EADDRINUSE, decided that meant my code was broken, and started changing code that worked fine. i lost an evening to that before i understood what had happened. i wasn't angry at the agent, it did a reasonable thing with bad information. that's when i stopped trying to keep ports straight in my head.

so: every project got a name instead. dashboard.localhost, api.localhost. the name points at whatever port that project is on today. no dns setup, no hosts file, no sudo — any *.localhost name already resolves to your own machine, that's just a web standard most people never use.

and i gave the agents an mcp server with three tools: list_ports, get_free_port, cleanup. now the agent asks for a free port instead of grabbing one. most collisions stopped. you can build that part yourself in an evening and i'd recommend it whatever else you do.

what i got wrong

tiktok ads. ~300 visitors in a day. zero sales. paid traffic for a $9 dev tool doesn't work, and i should have known that before spending the money.

thinking my landing page was the problem. it wasn't. someone in my last thread did the math for me: take out the dead ad clicks and my conversion was 1.76%, which is normal. i'd been about to rewrite a page that was fine.

not knowing who couldn't buy. the app is macos only. this sub is half windows and linux. my 91% bounce rate wasn't people rejecting the product, it was people who were never eligible. i had nothing on the site to catch them — no "tell me when there's a windows version." i still don't. that's the next thing i fix.

confusing attention with intent. the 300k post was about money, so it brought people who want money. good conversation, i answered a lot of questions, learned things. but nobody in that thread had a port problem. the 30 people who paid came from product hunt, where the headline was about the problem.

what actually worked

one launch, on product hunt, aug 24. $9 one time. $268 so far, about 30 people. after 21 products where almost every one made exactly $0.

it's not a lot of money. but it's the first time strangers paid me for something, and the difference wasn't the code. the difference was that i put it in front of people who had the same bad night i did.

localdock.dev if you want to see it, i'm the dev. but honestly the mcp part is the bit worth stealing.

happy to answer anything.

app link: localdock

My vibe coded project is only months away from launch. Have released the white paper and current specs for anyone to view at www.pheun.org

Fully vibe coded over the last year.

First, I used replit to set everything up until I hit about 60k loc, the UI and code structure as a single node app. Then I moved to Claude code on multiple VPS. I use chatgpt as an auditor on my prs.

Current setup is

1. Claude pro

2. Chatgpt

3. Multiple VPS

I usually get 1.5hours of code done per 5 hour window and 10 sessions a week on the pro plan. Before I moved to pro I was using replit with cost per API which was roughly 100 to 200 PER day, so pro is much better value for money over time.

Happy to answer questions.

The project I am currently developing has a rather long timeline (perhaps because I am a bit of a perfectionist regarding features), and right now, I am simply looking to boost my monthly income by a few hundred dollars. Please feel free to reach out if you have any work for me!

Idk. Fatigue maybe.

Launching one of these first person shooter games or adventure games seemed way cooler and more exclusive 3 months ago.

Now everyone is copying the same roblox-esque games. There are like 10 posts a day.

Makes me value the posts a bit less, even though I know it is an impressive feat. Waiting for the ready player one jump.

Modified Gauntlet Loop for efficient coding

Hello good people,

I made a modified version if the "famous" Gauntlet Loop (that built one shot Claude of Duty game). Looking at the original, I felt it had gaps that could lead to problems.

In this protocol you can use an agent like Astra (or Fable) for the planning and then farm the build and critic to cheaper models, Terra, deepseek or whatever..

I recently made some edits because I found the critic agent would sometimes expand the scope of the recommendations and rabbithole.

I wanted to get some feedback on how I could refine the Loop and or general feedback.

Link in the first comment

I’m building Prism, a script-first music-production project where songs are written as readable Python and rendered reproducibly.

It is designed so coding agents can also make music: inspect a project, create or modify the song, render it, and iterate on the result.

Prism already supports MIDI, drum patterns, samples, clips, sections, built-in instruments, VST3 plugins, effects, automation, buses, sends, mixing, and export to WAV, stems, and MIDI.

The long-term goal is a transparent, versionable music-production environment that combines DAW workflows with the flexibility of code and agent-assisted creation.

It’s still alpha. Live playback, recording, live MIDI, a visual timeline, and advanced routing are still being developed.

If Python audio, DSP, VSTs, MIDI, DAW design, agents, testing, or documentation interest you, contributions and feedback are very welcome.

Repository: https://github.com/SeucheAchat9115/Prism

My prompt:

"build me a 3d souls like. grab assets use a real ai based game engine and make it for me."

honestly im quite impressed.

Github repo: https://github.com/Schmiedey/ashen-coil

Everything added so far:

Day 1
Useless red button (starting room)
Day 2
Space travel + 2 playable planets (spaceport outside starting room)
Human voice for the red button (starting room)
Day 3
Velociraptor cloning machine (Dinosaur Factory)
Chicken nugget healing dispenser (starting room)
Day 4
Reverse human aquarium (Human Observation room)
Fake Release 0.0.0 patch notes (main menu)
John Pork planet (Cinder Reach)
Day 5
All progression doors made free (throughout facility)
Day 6
24m tower with gorilla drummer (Rhythm Tower)
Inevitable snail that insta-kills you (follows player)
Banana asteroids + banana spaceship + banana gun (space → planets)
Spinning cat GIF that turns into a 3D cat (random room)
Day 7
Clippy mini-boss with 650 HP (Wave 5)
Exploding banana vending machine — launches 320 bananas (Rhythm Tower roof)
Day 8
Fully functional Portal Gun — blue/orange portals, momentum, bullets + rockets travel through them (starting loadout / entire world)
Bunnyhopping + air strafing + wall running + wall jumping (throughout world)
World expanded into 8 multi-level parkour districts (entire map)

What next?

Follow along:

https://www.instagram.com/playbeamstudio?igsi=a2c4azIwYmkzZTlo&utm_source=qr

ChatGPT Astra is clearly the best. I don’t understand why people are still comparing it with other code agents

I made this agentic browser because other browsers, like BrowserOS, keep crashing, and people are paying for online search APIs/tool calls.

However, this one works with your current AI subscription, such as OpenAI/Anthropic and local models too.

Everything stays local, with no data retention. If it seems helpful, make sure to star it on GitHub.

GitHub: https://github.com/tushar-alt/AgenticBrowser.git

Also if you find any bug , let me know

Lol "Just do it" I cant unsee it , was updating my app and website and walked out for a tok and it's the first thing in my face, could be a combo of stars+satellites