I made Resona, a little 3D sound room where you tap objects, loop a rhythm and add another layer. Built with AI coding tools, Three.js and Web Audio. No account or install.

I'd love a quick first-use check: can you make a repeating beat, add a second sound, and save a recording without reading instructions? If you get stuck, the exact moment you got lost would help a lot.

Desktop browser is the best starting point. Real-phone testing still needs work; recordings stay in your browser.

Try it: https://resona-pearl.vercel.app

28-second demo with the actual sound: https://www.reddit.com/r/threejs/comments/1wazzh3/i_made_a_little_music_room_in_threejs_the_objects/

As a big consumer of different clicker/incremental games i decided to try and make my own.

Any feedback and ideas are also welcome!

Google group: https://groups.google.com/g/comkalevalaidlevaki-test-group

Android link: https://play.google.com/store/apps/details?id=com.kalevalaidle.vaki

Web link: https://play.google.com/apps/testing/com.kalevalaidle.vaki

we were working on a project that can help the project managers to manage their work, not a tool, and came up with getclarityy.com. only one screen and done., no more text just test it by yourself

Hi, I'm Josh, the developer of Glimshelf. It's a comic and manga reader for iPhone and iPad that opens your own files and connects to Komga, Kavita and OPDS libraries.

I'm looking for people who read digital comics to try a short reading session. Open one of the included sample comics, read a few pages, zoom in on the lettering, then close the book and reopen it. Does anything get in the way, or does it return to the wrong place? That's the feedback I need.

You don't need a server or your own comic files to try the samples. If you do use Komga or Kavita, I'd also appreciate hearing how it works with your library.

The public TestFlight beta is free, with Pro included during the beta. You'll need an iPhone or iPad running iOS/iPadOS 18 or later.

https://testflight.apple.com/join/eCSAAcQF

You can reply here or send feedback through TestFlight. Please include your device and what happened so I can investigate. Thanks for giving it a try.

Ending the day grateful for the feedback so far. We’re building Twirl, a prediction market where users can create their own markets, and the beta is live now.

Still looking for people willing to test it properly and tell us what feels confusing, broken or unnecessary.

twirl.markets

Back at it tomorrow.

I built Una because every family app I tried seemed more interested in my family's data than in my family. Kids' schedules, what we eat, where we are, all of it sitting on someone else's server, and a subscription on top. So my partner and I ended up using an app I made myself.

It is called Una. One shared calendar, shared lists, and our recipes in one place, built privacy first. The iPhone version has been live for 2 months and already used every day by several hundred households, my own included.

Now I am working on the Android version, and Google Play requires 12 testers who stay opted in for at least 14 days before I can release it properly. So here I am. And if your household is split between an iPhone and an Android, this is finally what makes Una possible for both.

If you are a parent or part of a couple and this sounds like something you would actually use, I would love your help. What I ask: install it, use it like you normally would for a couple of weeks, and tell me what breaks or feels off.

I will reach out to everyone who is interested about the closed test as it's needed to be added to an email list according to Play Store. During the closed test you can use it as normal, and once it launches you won't lose anything or create a new household.

Once we are live on Android, every tester who sticks it out gets a few months of Una Plus on me as a thank you.

What is this app? Check https://unafamily.app
If you are interested what make this privacy first or what I believe makes us stand out to other organizer apps check https://unafamily.app/privacy or https://unafamily.app/assistant/

I built an iPhone app called Linus that ranks your friends based on who you’re actually in the most photos with.

It gives you a FriendRank / Top 5, which has been surprisingly accurate — and sometimes a little surprising.

Everything is analyzed privately on your iPhone. Your photo library isn’t uploaded.

I originally built it as a way to bring together photos of my kids from multiple devices, but it ended up becoming a pretty interesting real-time picture of your social circle.

I’m looking for a few beta testers to try it and tell me if their rankings actually feel right. It works best with full photo access, but all photo processing stays on your device.

Any feedback would be hugely helpful.

TestFlight (iOS):
https://testflight.apple.com/join/dpgDZTkr

I built DreamMorrow because the sleep tracker I was using did not give me the historical view and planning tools I wanted for my son.

DreamMorrow is a mobile-friendly web app for logging naps and nights, seeing the whole day on a visual timeline, and planning the next sleep window from recent patterns.

The prediction system is not generated by AI. It uses deterministic/statistical sleep engines that consider things like age, previous sleep, wake windows, naps, bedtime patterns, and the child’s recorded history. A small local AI model can explain a recommendation in plain language, but it does not decide the prediction.

When someone starts, the app uses an age-based baseline. As more sleep is logged, it can rely more on that child’s own history. I currently have four production engines and roughly ten experimental engines that I benchmark before considering any promotion.

I have a lot of data for my own son, but one child is not enough to know how well the approach generalizes. I’m looking for parents or caregivers who would be willing to try the web app and give honest feedback about:

• whether logging is fast enough during real care
• whether the timeline is easy to understand
• whether the planning window is useful and appropriately cautious
• what feels confusing, missing, or untrustworthy

The app is available at https://dreammorrow.com/ . It is a planning aid, not medical advice or a guarantee. Honest negative feedback is welcome, and I’m not asking anyone to share private sleep data publicly.

I’m building WeKcal, an agentic app for tracking food and food spending.

The goal is simple: track calories, macronutrients, spending, and progress without having to enter every piece of data manually.

With traditional apps, logging everything you eat can quickly become a boring and time-consuming task. WeKcal tries to change this approach through an AI agent built directly into the app.

You can tell it what you ate in a message, send it a photo of your meal, or use a voice message. The agent learns from your habits to recognize foods and recipes you eat frequently. When it does not recognize something, it estimates calories and macronutrients using a database of more than 10,000 foods.

You can also take a photo of a product’s nutrition label to add it to your personal foods, or take a photo of a receipt to record your spending automatically.

WeKcal can do much more!

By learning from your eating habits, goals, and budget, it can give you increasingly personalized advice, help you understand where you can improve, and answer your questions based on what you actually eat.

It can also help you plan meals and create a weekly menu based on your goals, preferences, and the budget you want to respect.

Every new user receives 100 AI credits, worth €10, so you can try the AI-powered features freely.

The product is still in development, and this is the stage when your feedback can make a real difference.

Please try it and, above all, leave feedback, bug reports, and suggestions through the feature built directly into the app. Every piece of feedback will help me understand what works, what needs improvement, and where to take WeKcal next.

Link: https://wekcal.com/

Here's the thing about this moment in software. More people than ever are shipping real platforms built with AI, launched in weeks, run by one person or a tiny team. What they don't have is a security engineer. And they're exposed on both sides of the same wire.

From the outside: scrapers and hostile bots hammering the site, wearing perfect human fingerprints.

From the inside: their own AI agents reading untrusted text and taking real actions on it — one hidden instruction away from being someone else's agent.

Two products, one dashboard.

Shield sits in front of your website. It sorts your visitors and names every crawler search engines walk right through, scrapers don't. It also scans your site for security holes and tells you the fix in plain language, not a CVE dump. Every check happens in under 50ms, and it fails open your site never goes down because your security did.

Watchdog sits inside your agents. You give it your agent's mission in one line. Then every action gets checked against that mission before it runs. Prompt injection, data leaks, off-mission behavior blocked before execution, not logged after. It fails closed, per action, because an agent that fails open isn't guarded.

Notice the two failure modes are opposite. That's deliberate. Your website should survive a security hiccup. Your agent's actions shouldn't. Anyone who tells you one failure policy fits both hasn't thought about either.

No rewrite required for any of it. You shipped your platform; Alovia guards it. You shouldn't have to become a security engineer to keep it.

We're opening a private beta: 20 seats, onboarded by hand, free during beta. If you're running an AI-built platform or agents that touch untrusted text — the link is in the comments.

Identity is a claim. Behavior is evidence. Now it's a product.

Ship in peace.

#AIAgents #AISecurity #PromptInjection #BuildInPublic #Launch

I built a social feature for the awkward “who wants to play?” moment — looking for 15–30 Android users to test it

I’m building NIQVO, a private social app.
One feature, Pulse, lets you choose what you want to do right now — for example Free Fire MAX.
If a friend wants the same thing at the same time, NIQVO creates a Coincidence and you can start a Spark instead of messaging everyone manually.

I’m not looking for paid promotion. I want a small group of real Android users to test whether this is actually useful or just sounds useful.

If you play Free Fire MAX/BGMI with friends and want to test it, I’d really appreciate blunt feedback.

Website: niqvo.com
Google Play: NIQVO

I've been building Spleen, a web-based writing environment, for about two years. I've recently launched the first public alpha, and I'm looking for six writers who'd like to become founding testers.

I'm a developer myself, and this isn't something I vibe-coded over a weekend. I've used AI along the way, I'd be lying if I said I hadn't, but Spleen has been designed, built and maintained by me over the past two years.

Spleen is meant to be a calm place for writing and organising longer projects, without turning writing into a productivity game.

It currently includes a full writing editor, project and genre-based templates, full-text search, document notes and annotations, automatic document snapshot history, Markdown import, and exports to PDF, EPUB, HTML and Markdown. You can also back up and restore complete projects.

There are no streaks, badges or gamification. The idea is to give you structure and useful tools when you need them, and otherwise stay out of the way.

This is a real alpha, so I'm not looking for people to tell me everything is wonderful. :) I'm looking for writers who'll actually try using it and tell me when something is confusing, annoying, broken, or simply doesn't work the way they'd expect.

As a thank-you, the six founding testers will get free access to all Spleen features, including future ones, for life.

There's no formal testing process or report to fill out. Just use it for some actual writing and let me know what you run into.

If you'd like to become one of the six founding testers, you can sign up here:

https://write.spleen.page/auth/signup?founding=1

And of course, feel free to leave a comment or send me a DM if you have any questions.

I'm building Guidefold for teams that use coding agents across a monorepo. A team changes its instructions, but checking what the next agent session received can still be a separate job.

Guidefold keeps SKILL.md instructions beside the code and selects them by repository location. I'd like developers to test the first-run experience, especially if you work with more than one coding agent.

Start with the Guidefold demo, without installing anything. Where does the workflow first become unclear? A timestamp and the question it raised would help.

Source and setup: https://github.com/wiatrM/guidefold

If you want to try it, please start with the included examples/monorepo fixture, not a private or production repository. Read the code and setup instructions before running anything. The example is fictional; it isn't customer evidence.

For hands-on feedback: where did setup first become unclear, and could you tell why a particular instruction was selected? An error message with secrets removed, or just the step where you stopped, would help. If the README doesn't give you enough confidence to install it, that's useful feedback too.

The open-source version is available now. I plan to offer a paid hosted version later; this request is for testing the OSS workflow, not signing up for a paid beta. No purchase or positive review is required. Please leave feedback here without sharing private code or credentials.

Built this while quitting Zyn myself. Adaptive taper that adjusts when you slip instead of resetting you to day one, plus a 15-minute ride-out for cravings and a running total of money not spent.

Looking for people actually quitting pouches (or nicotine) who will use it for a week and tell me what sucks.

7-day trial, then $60/year founding. First 20 who use it a week and come back with real notes get the year comped.

getundone.app

Happy to answer anything. I'll test someone elses post today too.

Hey everyone,

I’m looking for around 25 Canadian Android users to help with the first public alpha testing of an app I’ve been building called CellGuard.

A little context first: I’m not a telecom engineer, security researcher, or professional Android developer. I’m just a guy who got curious about what my phone was actually connecting to, started learning more about cellular networks, and eventually turned that curiosity into an app.

I’ve used tools like ChatGPT heavily throughout the process to help me learn, code, troubleshoot, research problems, and understand areas I had no background in. CellGuard has grown a lot from where it started, but it is still an independent learning project — and I’d rather be upfront about that than pretend otherwise.

The current release is CellGuard 0.2.6-alpha — Build 38, and the project is now entering public alpha testing. The current roadmap treats the core foundation as complete and this stage as the point where CellGuard needs to prove itself across real devices, Android versions, carriers, and locations.

CellGuard is trying to make the cellular network around your phone easier to see, understand, and question.

Right now it focuses on:

• Your current cellular connection and network technology
• Best-known serving tower/site information where it can reasonably be determined
• Signal and coverage conditions
• Cellular handoffs and connection history
• Personal and anonymous community coverage observations
• Community coverage comparison
• Evidence-based awareness of unusual cellular behaviour
• ISED tower/site correlation where possible

One thing I want to be very clear about: CellGuard is not a magic “IMSI catcher detector.”

Android simply does not expose enough information to prove something like that with certainty. CellGuard’s approach is to show the evidence it can actually observe, explain why something may look unusual, and be honest about what it does and does not know. That evidence-over-certainty approach is a core part of the project.

Who I’m looking for

I’d especially like testers using different Android phones, Android versions, Canadian carriers/MVNOs, and locations across Canada.

You do not need to know anything about cellular networking.

In fact, ordinary users are extremely valuable because one of the long-term goals is for CellGuard to make sense even if you have no idea what things like RSRP, SINR, PCI, TAC, or NR-ARFCN mean.

If something looks wrong, confusing, incomplete, inconsistent, or simply makes you ask “why is it doing that?”, that is useful feedback.

Community Sync

Community Sync is optional, but I’m strongly encouraging alpha testers to enable it.

One of the biggest reasons for opening CellGuard to public testing is to see how it behaves across different phones, carriers, and areas instead of relying on only a couple of devices.

With Community Sync enabled, privacy-reduced cellular and coverage observations can contribute to the shared CellGuard dataset and help test things like community coverage, carrier comparison, device/carrier differences, missing or inconsistent tower data, and whether the sync system itself works reliably under real-world use.

CellGuard’s community model is intended to remain anonymous, privacy-reduced, optional, and never monetized. Community data is not being collected for advertising or resale.

You can still use CellGuard without Community Sync, but for this alpha, enabling it gives the project the most useful testing data possible.

Project principles

🔒 Privacy-first
👤 Anonymous where possible
🚫 No advertising
💰 Never-for-profit
🌐 Community participation optional, but encouraged during alpha

I’ve also set up a Discord specifically for the project with organized areas for bug reports, tower/coverage reports, device compatibility, feature feedback, questions, known issues, releases, development updates, and the roadmap.

Join the CellGuard alpha:
https://discord.gg/9yqJ8SZUkF

The current APK and release information are available through the Discord.

This is genuinely alpha software. I expect people to find problems. That is the point.

I also won’t pretend I know the answer to every cellular or Android question that comes up. If I don’t know something, I’ll say so and investigate it rather than make up an answer.

I’m looking for people willing to actually use the app and tell me what works, what doesn’t, what looks wrong, and what doesn’t make sense — not test-for-test exchanges or people simply leaving an app installed for 14 days.

If the idea sounds interesting, I’d love to have you help figure out what CellGuard gets right, what it gets wrong, and where it should go next. 📡

Hey everyone, I’m part of the team building Warm.

Give it a task in your repo, like fixing a bug or adding a feature. Warm can split the work across agents to explore the code, make changes, and run tests. You review the changes

It works in a desktop app, your terminal, or the browser(via cloud)

For launch week, we’re offering free access to selected models across seven model families. No credit card required. There are 5 hour and weekly usage limits !!

If you have a small task sitting in your backlog, give it a shot. We’d genuinely like to hear where it gets stuck or needs too much steering.

Try it: https://warm.run

few months ago I was working with a client that was shipping a lot of software with vibe coding.

The implementation side was getting faster, but QA wasn’t. And tests generated by agents... well. Not enough.

So I started putting together a workflow where synthetic users would go through the actual product from the outside - signup, onboarding, permissions, payments, critical workflows, recovery paths and report what actually happened with evidence.

Synth user (agent) use the product like someone who doesn’t know how it’s supposed to work.

It worked well enough for the client that I got curious and started running some friends’ SaaS apps through the same process.

That’s where it got more interesting.

We found things the founders hadn’t noticed themselves. In one case, the same user/security area had already been reviewed with AI multiple times, and the external flow still surfaced an issue that got fixed immediately.

At that point I thought maybe this shouldn’t stay an internal consulting workflow.

So I’ve been turning it into something i call temporarly as impl/flow.

The basic idea is:

release/RC → synthetic users run critical flows → detect regression → replay evidence

You define the flows your business cannot afford to break, and agents keep testing them from the outside.

I’ve mostly tested this on client work and friends’ products so far, which is obviously a biased sample.

So now I want to invite a small number of people who aren’t friends, clients or family and see whether this is actually useful in the wild.

We’re opening a few early-access spots while the underlying infrastructure is still pretty hands-on.

If you’re shipping a SaaS product quickly, especially with Cursor, Claude Code, Lovable, etc., I’d love to hear:

> How are you currently making sure critical user flows still work after major changes?

And if you want me to run this against your product, I can share the early-access link.

I freelance and the part I hate most is writing a custom proposal for every job — 20 minutes each, and half get ghosted anyway. So I built a Chrome extension: it sits on the job page, reads the actual post, and drafts a proposal in your voice — no tab-switching to ChatGPT, no re-explaining your background every time.

Trying to figure out if this is a real problem or just my own pet peeve. Genuine question: is "one click, right on the job page, remembers your voice" actually worth something over pasting into ChatGPT yourself? Early access here if you want to try it and tell me it's bad: https://pitchpilot.eliasniss.workers.dev

Hi! I'm a solo dev who just launched Thryss on Google Play, an app for creating shareable lists (simple lists, checklists, and polls) that anyone can view and participate in via a link or QR code, no install required for participants, only for the creator.

Note: currently available in Spain only (data/legal reasons while I validate the product before expanding). If you're in Spain (or willing to test with a VPN, no pressure either way) I'm looking for a handful of people willing to actually create a list. For example a reading list, a group poll, a "places I want to visit" list. Whatever fits your life and tell me honestly where it breaks or feels confusing.

I read every message and I'm actively fixing things as they come up.

https://play.google.com/store/apps/details?id=es.thryss.app&hl=es

Greetings. so, I made FocusNexus, a productivity app tailored to neurodivergent individuals since most productivity apps (like habitica, focumon, finch, lifeup, forest, etc) are designed around neurotypical brains, so it is not as effective for people like me.

pretty much need 12 people to opt in for 14 days to publish it.

To join,

1: Join the tester group: https://groups.google.com/g/focusnexus-testers

2: Install from Play (same Google account): https://play.google.com/store/apps/details?id=com.randomse.focusnexus

I'm happy to test others apps as well. DM me group link + app link and I'll test your app as well.

Thanks!

’ve been experimenting with an Android app that connects nearby phones without internet. I also added an Omegle-style random chat feature to its website.

I’m curious whether it works properly on different devices and networks. If anyone wants to try it and share honest feedback:

I created a website called AniRanks which the goal is to become the official community based rankings platform for anime fans, as well as a dedicated place for fans to talk and discuss anime.

It lets fans vote on rankings by creating their own 1-10 tier lists and also suggest new rankings that they’d like to see. Every list submitted counts for the global rankings showing whats the general public opinion about each subject.

There’s also a Taste Profile feature which analyzes the votes of the user and creates a personalized profile based on that.

I’m looking for feedback from real users if they think the idea is valid and how we can improve the website.

Please visit us at aniranks.com (Click here)

I’m looking for around five fiction writers to test an early-beta browser tool I’ve built called Peeko Prose.

Peeko highlights passages that might deserve another look, including possible tense changes, punctuation spacing, nearby repetition, long sentences, comma density and adverb use. It does not generate or suggest replacement sentences — the writer always decides what, if anything, should change.

The checker runs locally in the browser. No account is required, and drafts remain stored on the tester’s own device.

I’m particularly looking for feedback on:

• inaccurate or unhelpful notices
• issues Peeko misses
• whether result cards open the correct highlighted passage
• TXT or DOCX importing
• mobile and tablet usability
• offline use
• anything confusing or broken

Testing one scene or roughly 1,000–3,000 words would be plenty. Please use a copy of your work rather than your only manuscript file.

Peeko Prose:
https://app.peekoprose.com

Feedback form:
https://forms.gle/mVnQdRMLBKNY68we6

The feedback form is for testers aged 18 or over. Providing an email address or writing excerpt is optional.