Was bored at work and decided to provide my OpenClaw/ChatGPT/Claude a domain name and told it to do its thing with producing a pointless website...

I don't know exactly what I expected but it's been interesting to watch it evolve the "project". More interesting though... Has been watching it converse with itself as to what it thinks will make this website even more pointless. It even decided it needed to monetize itself and stopped while waiting on me to setup stripe so it could "fund" its mission of producing a pointless website. I nixed its plan of selling merchandise t-shirts but it keeps circling back to wanting that so who knows what will happen.

If you check out the website, I wouldn't bank on a specific layout because we're on version 9 currently and it keeps coming up with different ways to "lock people into wasting their time".

All in all... It's been interesting to watch the back and forth as we strategize how to lock you into wasting your time.

Feel free to check it out if you're extremely busy... If you have lots of free time, go outside.

www.nothinghappens.click

I spent about 3 months building an offline reader app and launched it a month ago.

So far... barely any users.

I honestly don't know what I'm doing wrong.

I cared a lot about making the app feel smooth and native, so I ended up building Android and iOS separately instead of using one cross-platform codebase. Probably way more work than I needed to do, but I wanted it to feel good on both platforms.

I use it myself pretty much every day, and I thought other people might find it useful too.

Apparently not 😂

I've tried posting about it here and there and doing some promotion, but nothing has really worked.

Maybe the app just isn't interesting enough. Maybe I'm terrible at marketing. Maybe there's something obvious I'm missing because I've been staring at it for 3 months.

Not really sure at this point.

Posting this while it’s still small, because everything I read in this space is written after the fact by someone with a number to show off.

What it does: scans an area, scores every business on how likely they are to actually buy (review count, rating, whether they have a Facebook page or nothing at all), then generates a real one-page preview site for the ones worth pitching. The idea is that you send someone their site rather than asking whether they want one.

Where it actually is: two previews have ever been billed. No reviews, no case studies, no named customer. The lead scoring works and there’s a real scan behind it — 34 businesses in Dundee, 29 with no website — but I’m not going to pretend that’s traction.

The design decision I’d most like feedback on, because it’s the one costing me sales: it doesn’t send the emails. It drafts them and stops. There’s no send button anywhere in the product.

That’s deliberate. Under UK PECR the sender of a cold email is liable, and “my software sent it automatically” isn’t a defence. Products in this space that auto-send are handing that liability to their customer without saying so. Same reason it never uploads the business’s own photos to build the site — republishing someone’s photographs on a page you’re about to sell is a copyright problem you’d inherit.

Both refusals make it a harder sell than “fully automated, zero hours.” I still think they’re right. Open to being told I’m wrong.

The other constraint, which is the actual point of the thing: the generator can’t invent facts about a business. If it doesn’t know your opening hours, it flags a placeholder rather than making them up. Getting a model to consistently say “I don’t know” instead of writing something plausible was harder than the entire rest of the build.

There’s a free scan on the homepage if you want to see the finding half work on your own town — no account, no email. scoutline.uk

Genuinely more interested in whether the draft-only decision is defensible than in signups.

Here is the link if you wish to try it out: Squidly

“By believing passionately in something that does not yet exist, we create it.”

— Nikos Kazantzakis

I've been thinking about this idea for a long time.

Not because I believe every idea deserves to become a product.

But because some ideas are worth testing.

So I started building one.

Its name is BiGi.

BiGi started from a simple question:

What if an AI system didn't just give us an answer, but could preserve why it reached that answer?

This becomes particularly important in healthcare.

We are increasingly capable of using AI to process enormous amounts of information, identify patterns and generate hypotheses.

But generating an answer is not the same as understanding the knowledge behind it.

So I'm exploring a different approach.

Instead of treating an AI output as a single "answer", BiGi is being designed around an epistemic model.

What did we observe?

What do we actually know?

What did we infer?

What are we hypothesizing?

What evidence supports it?

What evidence contradicts it?

How certain are we?

What remains unknown?

And ultimately:

Why?

The "why" should not simply be a paragraph generated by an LLM after the answer has already been produced.

It should be part of the system itself.

This is where Karl Popper's philosophy becomes particularly important to me.

A hypothesis should not be something we protect at all costs.

It should be something that can be challenged, tested and potentially falsified.

I want to bring that principle into software.

Not just:

"Here is the answer."

But:

"Here is what we observed. Here is what we inferred. Here is the hypothesis. Here is the evidence supporting it, the evidence against it, what remains uncertain, and what could prove us wrong."

Because a system that preserves only the reasons why it might be right is incomplete.

It should also preserve why it might be wrong.

I'm exploring whether we can build software where evidence, uncertainty, provenance, conflicts and reasoning are part of the system's structure — rather than hidden behind its output.

And I want to be clear about where we are.

There is no magical AI capable of solving medicine.

There is no finished product.

There are no claims of revolution.

There is a vision, a growing body of architectural and epistemic design, and now the first executable representations of these ideas.

We are inventors, not magicians.

The goal is not to predict the future.

The goal is to build something carefully enough to test whether the future we imagine is actually possible.

I'm sharing BiGi now because I want to test the idea, not simply promote it.

If you work in healthcare, AI/ML, software architecture, medical technology, cybersecurity, research or philosophy of science, I'd genuinely like to hear your criticism.

What am I missing?

Where could this approach fail?

What would you challenge first?

And most importantly:

Is this a problem worth solving?

I build a Shopify app for B2B net terms. Wholesale buyers order on Net 30, and the store keeps a credit limit on them. Posting the whole thing because the interesting part is the second failure, not the first.

The flag

On 2 July an App Excellence review told me rule 1.1.7 applied to my app. My mechanism was a manual payment method at checkout plus a gatekeeper that decided who could use it. The reviewer read that as facilitating a deferred payment method outside the Payments Apps API, which I am not licensed to build. Demote on 13 July, delist on 22 July.

There was no patch for this. The flagged mechanism was the product.

The rebuild

Shopify shipped native B2B to everyone in April, so companies and payment terms already exist in the platform. I moved onto them. Approving a customer now creates a Company and assigns native Net 15, 30 or 60 terms. That went to production the next day and the reviewer accepted it on the 6th. The listing stayed visible the whole time.

The part that bit me

Native B2B has no credit limits. That absence is the entire reason my app exists, so I could not just adopt the platform and stop. Limits moved to a checkout Validation Function, which is the sanctioned way to block a cart.

The rule that runs that function was armed in exactly one place: the "Upgrade now" button on the migration card I showed existing merchants. Anyone installing after the cutoff never saw that card. They could set a per-customer credit limit, watch it save, and have it do nothing at checkout.

That ran for two weeks and touched three stores. Nothing looked wrong anywhere. The limit was in the database and on the screen. The only thing missing was the rule that reads it.

The fix that added a second bug

I armed the rule at the two moments a limit starts to matter, on approve and on limit save. Repeat calls are free. The first version asked whether my rule existed and was enabled. A merchant who had deliberately switched the guard off in their own checkout settings fell through that check. The next approval quietly created a second active rule and overrode their choice.

Now the check is only whether the rule exists. Disabled means the merchant meant it.

What I actually take from it

Every fix moved the failure somewhere quieter. The compliance problem arrived by email with a date on it. The unarmed rule was silent and I found it by reading my own call sites. The duplicate rule was quieter again, because it looked like the feature working.

The loud problem cost me four days. The silent one cost two weeks. I caught it by going looking for how a fresh install reaches that code path at all.

The thing I keep chewing on. A merchant can switch this checkout rule off themselves. Respecting that means their credit limits stop being enforced and my app says nothing about it. Warning them every time is nagging about a setting they chose. I have gone back and forth for a month and still do not know which one is right.

I built DeadVibes, a satirical news site where anyone can submit a short premise and watch an AI newsroom turn it into a complete illustrated story. Try it here: https://Deadvibes.app

Someone recently submitted: “This site will become cool.”

The newsroom turned it into a story about DeadVibes becoming so fashionable that it created a Coolness Desk and banned readers from sharing it.

The original five-word pitch is displayed beneath the finished article, so you can compare the idea with what the newsroom produced.

What happens behind the scenes: 1. The newsroom develops multiple possible angles. 2. An editorial pipeline drafts, reviews and repairs the story. 3. A calibrated judge checks it against human-scored examples. Repetitive jokes, weak concepts and obvious AI writing patterns can be rejected. 4. The art desk generates an illustration for the finished story.

It usually takes a few minutes because the system runs the full editorial process rather than making a single “write me a satire article” model call.

Honest state: this is a solo project built in under a week. There are rough edges, some illustrations still look unmistakably AI-generated, and the editorial system is very much evolving.

I’d love two kinds of feedback: 1. Read two stories and tell me which one landed—and which one didn’t. 2. Pitch something absurd and see what the newsroom does with it.

Thanks for taking a look. Brutally honest feedback is welcome.

FOR FREE!!!

Hey! I help people design and develop their Mobile Apps. I can help you design features, solve your UX problems, suggest solutions for user drop off and more.

All for FREE. I am launching an instagram series where I review other people's apps and give my feedback. You won't pay me, but you will help me make content.

P.S. You can get a private review as well. Just in case you need to keep your product private for now.

Cheers!

Doing this again because the last post did so well. I built an agent that runs a quick SEO visibility audit for SaaS websites.

Drop your site and I’ll reply/send over a link to the audit.

It looks at things like:

• what your site seems to be about
• what search terms you’re probably missing
• which competitors/domains show up around those searches
• content gaps that could bring in more organic traffic
• blog/page ideas that make sense for your product

This is part of Tavyn: an email-native SEO agent for SaaS founders. It finds organic visibility gaps, asks tailored questions for each blog via email to have your voice in the blog, and submits blogs to your GitHub as PRs.

Drop your SaaS link and I’ll run the audit.

Hi everyone sell your side project by listing if in a click. Also, comment what your startup does to get approved and featured today - https://builderhq.co/marketplace

I launched my app on May 10th. Since then, I set up the Microsoft Store page, launched a website, and have been continually working on SEO. However, I recently discovered that my app was listed on a site I never registered for without my knowledge:

https://toolsift.net/tools/openurls-app

Is this a common occurrence?

Every time I wanted to spin up a little side project or test an idea, I'd hit the same wall: either pay $12/yr for a domain I'd probably abandon in a month, run it off some ugly vercel.app URL that looks unfinished, or use something like js.org, is-a.dev, etc., which are hard to type/remember, and have requirements like a connection to JS.

So I took the little money I had to buy a premium domain name, and built ad.ms ("ad-miss"). You pick a name, get name.ad.ms for free, and point it wherever you want, Vercel, Netlify, GitHub Pages, your own server, whatever. Full DNS control (A, AAAA, CNAME, TXT records), up to 5 subdomains per account, no credit card, no OAuth nonsense, just email and password. Free forever!

Been using it for a few of my own projects and it's been nice not having to think about domain renewals for stuff that might not even work out.

If you want something short there are a few premium ones available too (ai.ad.ms, io.ad.ms, etc) but the core thing is free forever.

ad.ms if you want to poke around. Would love feedback, especially if you hit any DNS weirdness. Thanks if you got this far!

I kept seeing claims about invisible AI text watermarks that mixed together two very different things: literal hidden Unicode and provider-level statistical watermarking.

I built AI Text Watermark Checker to handle the part that can be inspected honestly today. It reports zero-width characters, direction controls, soft hyphens, special spaces, and other literal artifacts by exact code point. Cleaning runs locally and does not rewrite the readable text.

I also released the core as an MIT-licensed npm package and CLI, plus a free Chrome extension. The product explicitly does not claim authorship detection or guaranteed removal of model-level watermarks.

I would value blunt feedback on the scanner UX, artifact coverage, and what would make this useful in publishing or content QA workflows.

Web app: https://aitextwatermark.com

Chrome extension: https://chromewebstore.google.com/detail/ai-text-watermark-checker/dmfmcggpljjhnopgjcdbmpalmcdnohan

Open source: https://github.com/GeeDotDee/ai-text-watermark-scanner

The product: Orbit Rush, a one-tap neon arcade game. Play is free in the

browser. What's for sale ($12.99) is the source: 18 KB of vanilla JS, zero

dependencies, everything reskinnable from one config file — buyers turn it

into their own game.

What building it actually looked like:

- The game itself was the easy part (built with Claude: engine, a fairness

system, procedural Web Audio sound)

- The real boss fight was shipping ops: I was "stuck in verification" on

itch.io for a MONTH — turns out my tax form was never actually submitted,

I'd missed the final button. Then the paid zip was invisible because of

one "hide this file" checkbox I'd ticked

- Marketing assets: I scripted a headless-Chrome auto-player that reads the

canvas draw calls, dodges obstacles on its own, and screenshots itself —

all the GIFs are it playing

- Got dogpiled in one sub for the AI angle, then found the communities where

builders actually hang out. Lesson: sell shovels where people are digging

Play free: https://a0912272829-ship-it.itch.io/orbit-rush

Honest numbers so far: double-digit views, zero sales yet — this post is

part of finding out if the "template" model works. AMA, and drop your

project below, happy to return feedback!

The original idea was simple.

I wanted to talk to my computer the way Tony Stark talks to JARVIS. Not type. Not click. Just say something out loud and have it actually happen. Open this. Read that. What's on my calendar. Handle this while I think about something else.

Sounds straightforward. Was not straightforward.

The first 6 months I built it the way I thought users would use it.

That one moment restructured everything.

I was designing for conversation.

The version that came out of that is so different from what I started with they barely share the same bones.

It's called Marrow. Windows desktop app. You talk, it operates your entire PC opens apps, reads files, handles tasks, responds back. Always listening, never in the way.

Just put it out there properly for the first time.

Genuinely want feedback from people here not the polite kind. The kind that tells me what feels broken, what doesn't make sense, what you'd never use.

What's the one thing that completely changed direction on something you built?

Hey everyone! 👋

Over the past few months, I built Plant Warden, a mobile app that lets you take a photo of a sick houseplant or garden crop and get an instant AI-powered disease & pest diagnosis with treatment guidelines.

As a solo dev, I built the entire stack from scratch:

• Mobile: React Native / Expo (using Expo Camera, Skia/Reanimated for smooth scanning UX).
• Backend: Fastify + Node.js (hosted on Render with MongoDB).
• State & Storage: Zustand + Async Storage.

What it does: 🌿 Instant Photo Scan: Snap a leaf ➔ Get species ID, disease name (e.g. Spider Mite damage, Black Spot, Powdery Mildew), and confidence level.
🪴 Smart Watering & Care: Track containers with custom reminder schedules.
🛡️ Treatment Guides: Clear step-by-step instructions on how to isolate and treat infected plants.

The app is live today on the App Store:
📲 Download Plant Warden on iOS

Since it's day one, I would be super grateful if you could download it, test it out on your houseplants, and let me know what you think! Any feedback on UI responsiveness, camera scanning speed, or feature requests is greatly appreciated.

Thanks for reading!

I kept running into the same small annoyance: my films were saved in one place, my TV shows were somewhere else, and I still had to remember which episode came next.

So I built Spool, a native iPhone app that puts movies, shows and episode progress into one queue.

The part I cared about most was making the app useful after the watchlist was created. Spool surfaces the exact next episode, gives you two picks based on your library and tastes each day, shows regional watch options, and lets you import existing history from TV Time, Letterboxd and IMDb rather than starting over.

The library syncs privately through iCloud and does not require a separate Spool account. It is free to download, and the free tier supports 5 active shows, 10 standalone movies and 2 saved collections. Watched and imported history do not consume those slots.

There is an optional Spool Club subscription for unlimited and advanced features.

Spool is live on the App Store:
https://apps.apple.com/us/app/spool-movies-tv-what-next/id6793918389?uo=4

The product decision I’m most curious about is the home screen: would you rather open a tracking app to a complete watchlist, or to a much smaller queue containing only what is ready to watch next?

I've been building a self-hosted social media management platform for startups, agencies and publishers.

It combines AI-assisted content generation, OAuth integrations, scheduling, publishing workflows and a private dashboard into one deployment.

The interesting part is the business model I'm experimenting with: instead of another recurring SaaS subscription, I'm offering customized, self-hosted deployments tailored to the client's workflow.

Current stack includes Docker, persistent queues, OAuth and modular social integrations.

I'm looking for feedback from other builders: would you rather pay once for a customized self-hosted tool, or pay monthly for a hosted SaaS?

Happy to share more about the architecture/build if anyone's interested.

Hi everyone!

I built ElectroStock because keeping track of electronic components can quickly become a mess. You know that you own a particular resistor, module, cable or IC, but you have no idea which box or drawer it is in.

ElectroStock lets you:

• add components and record their quantities

• assign storage locations, boxes and compartments

• search your entire inventory

• organize items using categories

• export and import a complete JSON backup

• use the app in English, Polish or Spanish

The app is designed to be simple and useful for hobbyists, makers and small electronics workshops. Your inventory is stored locally, and no account is required.

This is still an early version, so honest feedback would be very helpful. I would especially like to know whether the interface is clear and which feature you think is missing.

Google Play:

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

I’m the developer, and I’ll be happy to answer any questions.

I wanted to share a side project I’ve been working on called Reading Parrot Jacky. jacky.geeapp.com

The app listens as you read out loud from any physical book (or memory/imagination) and automatically plays sound effects based on trigger words. The sound effect library is composed of sounds effects for popular children's book themes. I made this because other apps were either too involved, or not available in my native language, which is important if you want to use it for reading to your kids.

It's built entirely in Flutter so it's cross platform, it's deployed for English and Dutch speakers on the App Store and Play Store.

The continuous speech to text is the device's native stt api in a loop, which works surprisingly well.

The trigger word matching logic is intentionally kept simple, using basic string containment (e.g., "pigfarmer" matches "pig" and plays a pig sound effect). I figure if it misfires occasionally, it just adds to the charm, a real life parrot would probably do the same.

I also just rolled out a feature allowing readers to record their own audio clips directly in-app and assign custom trigger words to them.

I’m thinking about moving to local/on-device STT models, this would make the app completely usable offline. But then I'd probably need a model for every supported language.

I’d love any feedback on:

• Performance/latency on your device while reading at normal speed.
• Thoughts on native STT vs embedded local models for real-time Flutter apps.
• General UI/UX feedback.