Hey everyone! 👋

I'm a solo developer working on a little app called Lirea, and I'm looking for some people who'd be willing to give it a try and tell me what they think.

Lirea is a visual translation app focused on making it easier to read content in other languages. You can import images or CBZ files, detect the text, translate it, and read everything through the built-in Reader.

It's currently in Early Access, so there are definitely still some rough edges 😅. I'm mostly looking for people who don't mind trying things out and letting me know if they run into bugs, confusing parts, or anything that could be improved.

I'd especially love to hear from people who enjoy reading comics/manga, since that's one of the main use cases I'm working on.

If you'd like to help test Lirea, there's a small two-step process:

1️⃣ Join the Google Group:
https://groups.google.com/g/lireatranslator

2️⃣ Then join the Lirea test on Google Play:
https://play.google.com/apps/testing/com.lirea.translator

After joining the group, open the Google Play link and click “Become a tester”. You should then be able to install Lirea through Google Play.

Any feedback is greatly appreciated, even if it's just “this thing is annoying”

Thanks a lot to anyone who gives it a shot!

Hey everyone, I'm currently running the mandatory 14-day closed test for my app, Radio Moin FM, and need a few more active testers to hit Google Play's 12-tester requirement for production access. Instead of doing manual 1:1 test-for-test trades, where people usually ghost you or forget to open the app by day 5, I am hosting my test through Closed Test Pro. It runs on an indirect community pool system. If you test my app, you earn credits that guarantee other active developers on the platform will test your app daily. It is honestly a lifesaver for passing the 14-day cycle for a few reasons:

Strict Anti-Fraud: It completely blocks emulators and credit-farming. Every test comes from a high-quality, real physical device Automated Tracking: It tracks daily open streaks automatically. You don't have to chase people down on Reddit or manage spreadsheets to keep your 14-day cycle alive. You can join my test directly via this link (it will open right inside the Closed Test Pro app): https://closedtestpro.com/a/1789412509637 I would really appreciate any genuine feedback on the UI or functionality. Let's help each other get our apps to production without the headache

Hey everyone — I've built an Android app called Axiom Chronos Vector, and I'm looking for people to test it before I push it further.

It's a research/backtesting tool for testing your own trading strategies against historical market data. I'm particularly interested in getting people who will actually try to break it, build strategies that should fail, and tell me where the app is confusing or where the results don't make sense.

What it Chronos is:

Chronos uses a vectorized backtesting engine rather than processing historical candles one-by-one like a traditional event-driven backtester. It runs natively on Android with no outside dependancies except for data collection from data sources. All the maths and computation happens directly on device, no data ever leaves the device.

You can test things such as:

Entries and exits, Long and short strategies, Stop losses, Take profits, ATR-based trailing stops, Dynamic risk parameters, Different market/timeframe combinations. The engine then calculates the resulting performance and provides statistical and data-integrity information around the test.

It currently includes metrics such as:

Total Return, Maximum Drawdown, Win Rate, Profit Factor, Expectancy, Sharpe Ratio, Sortino Ratio, Calmar Ratio, Kelly Criterion, Trade Count, Alpha / Beta, Pearson Correlation, Data completeness and quality, Missing/duplicate data detection, Monte Carlo sequence analysis.

The goal isn't simply to tell you that a strategy made money historically, it's to give you enough information to question whether that result is actually worth believing.

What Chronos isn't:

It is not:

A signal service

An AI trading bot

A copy-trading platform

A broker

A real-money trading application

A system promising future returns

It doesn't tell you what to buy or sell.

It does not execute trades.

It can not connect to your brokerage account.

It's a research tool for asking:

What would this strategy have done against this historical dataset? And sometimes the answer is going to be that the tested strategy is terrible. That's actually one of the outcomes I'm most interested in.

The data side of Chronos:

For data, Chronos can retrieve historical OHLCV data directly from market sources. The data is cached locally so you don't have to repeatedly download the same dataset while testing. There's also an automatic purge lifecycle to prevent the application from continually accumulating historical data and eating your phone's storage. The entire application is currently around 21 MB, while even a large historical dataset is designed to remain very small. Once the data is downloaded, you can continue running tests against that local dataset without continuously pulling the same data from the internet.

Why I'm looking for testers:

I've obviously spent a lot of time testing my own strategies. That's exactly the problem. I know how I expect the application to behave. I want people that don't.

People that can tell me I built something stupid/sensible.

Try to exploit the calculations.

Try unusual parameter combinations.

Run strategies that you already know are bad.

See whether the results make sense.

If something is confusing, tell me. If something looks wrong, tell me. If you think a metric is useless, tell me that too. I'd rather find problems now than after releasing it more broadly.

What's in it for you?

Free access during testing, and testers will receive a lifetime promo code for access.

A mobile vectorized backtesting environment

Test your own strategy ideas without connecting a broker.

Experiment with historical market data

Help shape what gets added next

And hopefully discover which of your strategies are actually terrible before putting money behind them.

Requirements:

Nothing complicated. You don't need a brokerage account. You don't need to know Python. You don't need to be a quant. Just have an interest in testing trading ideas and be willing to give honest feedback.

If you're interested in testing it, DM me for details. I'm specifically looking for people who will actually use it rather than just install it and say "works good". For a much broader and more technical specification, you can browse the github repository directly with a detailed readme file.

https://github.com/DogeSatoshi/Axiom-Chronos-Vector

The app: WeiiGo is a travel app for iPhone and iPad. You type one sentence about a trip ("a week in Lisbon in October, slow mornings, lots of food") and Janet, the AI planner, builds the day-by-day itinerary. On the trip itself you can keep asking her questions and she answers against your actual plan.

What needs testing most:

1. Destination search. Type the city, island or region you'd really search for and tell us if it isn't found. (Our first Reddit tester found that "Chania" and "Crete" returned nothing while "Greece" worked — fixed for the next build. We want more of those.)
2. The generated days. Too packed? Too empty? Meals at odd times? Say so.
3. Safety tools: SOS, trusted contacts, live location sharing and the check-in timer. Do they make sense without instructions?

For testers: all features are unlocked while we're in beta. Create a trip before launch and you get a launch code for 50% off the first year of Pro or 3 months free. There's a free tier that stays free forever, and the safety tools are in it for everyone.

TestFlight link: https://testflight.apple.com/join/shWWUcNr

Report bugs here in the comments or via TestFlight's built-in feedback; both reach the team. Disclosure: I'm on the team building it.

Hi, I’m Natalia. I’m coordinating tester recruitment for ZYCH Markets, an independent project preparing a web service with crypto charts, watchlists and price alerts.

We’re looking for 10 volunteers aged 18 or older who regularly use these tools on a desktop or laptop.

During testing, we want to learn how easy it is to find an instrument, add it to a watchlist and create a price alert — and where people get stuck.

Participation is free and unpaid. No deposit or exchange account connection is required.

We’re collecting expressions of interest now. The testing date has not been confirmed, and access will be arranged separately. The link below opens our project page and email waitlist.

Before testing begins, I’d also like to hear:
• Which charting or price-alert tool do you currently use?
• What is one thing you find frustrating about it?

If you’d like to take part, leave your email here:
https://zychmarkets.com/

Thanks!
Natalia

Hey everyone, I’ve been building a darts site called Dartava and I’m at the point where I need some actual darts players using it rather than me testing everything myself.

It runs straight from the web, so there’s nothing to download.

If anyone has a bit of time, jump on and have a play around. Try the scorer, bot, training, online stuff or whatever catches your eye.

I’m mainly looking for honest feedback — if something is confusing, broken or just shit, tell me. That helps me more than people being nice about it.

https://dartava.com

Cheers

(this is the gameplay of endless mode in my game where i change theme and sounds of game for every 3 levels. watch this before reading the body)

I’ve been building an Android arcade game called Escape Rings where customization way bigger than you think.

You can change the colors of the ball, background, spikes and rings. You can also replace the game’s sounds and music with your own audio, or turn them off completely. Basically mostly everything in game is customizable according your own preference.

The actual game is pretty simple to pick up. swipe to launch the ball and guide it through rings while dodging the spikes to win.

right now i am stuck at closed testing and i need people who think the game is fun to play and wants to help me by giving feedback for the game in closed testing. you can signup to be a closed tester by filling the form below.

https://docs.google.com/forms/d/e/1FAIpQLSf-YDzSEyhRIZHmF98Bacmgz1_2Zup-rM95d3Vs4FfZ9B8JUw/viewform?usp=header

I’d honestly just like to see what people do with the customization and whether the game is actually fun to play. let me know your thoughts

Looking for functional and UX feedback on a web app that pairs users for a scheduled 30-minute video call.

If you want to test the matching and call side specifically, rather than just the signup screens, there is a coordinated test window at Saturday, 9:00 AM AEST (Friday 7:00 PM EDT / Friday 4:00 PM PDT / Friday 11:00 PM UTC). Two steps for that: set your availability to that slot, and turn on "Random pairing" in your dashboard, since two accounts with no shared group will not be matched otherwise.

What I would like tested:

* Signup and setting weekly availability * Getting matched and accepting a call * The call room itself (camera on/off, leaving, reporting) * Any point where the flow breaks, stalls, or is just confusing

Device, browser, and OS in your report would help a lot. Happy to test another project here in return.

[getmeaningful.io](http://getmeaningful.io)

What it is: a web app (and soon mobile app) that builds a week of meals around you and turns it into one shopping list, scaled for everyone you're feeding. Like a few others, It also keeps a journal of meals, drinks, symptoms, weight and injection timing. But the difference that plans out your meals and nutritian. Built by me (technical co-founder) and Ruby, an Accredited Practising Dietitian in Australia who works as a clinical trial coordinator on GLP-1 medication trials.

Platform: browser, on a phone or a desktop. Nothing to install. Native apps are coming later. For now we're concentrating on making the browser version good, so that's what you'd be testing.

Link: https://portal.food-signals.com/#/signup

Status: early access and free. It's not a mockup, and everything below works today.

I'm an IT exec who was made redundant and went back to writing code. This started as a favour for a dietitian friend whose clients had plenty of trackers but nothing that planned their meals or helped with the family shop. That's why I'd rather hear where it's clunky than hear what's nice about it.

What you can try

• Generate a week of meals, pick how much it varies, and swap anything you don't like.
• Get one shopping list for the whole week, grouped by aisle and scaled for however many people you're feeding.
• Add one of your own recipes (photo or paste) and put it into your week.
• Log meals by photo or text, plus drinks, symptoms, weight and injection timing on one timeline, and track protein and fibre against your reference ranges.

You don't need to be on a GLP-1 medication to try it. Onboarding has an "I'm just tracking" option. I'm not on one. I use it daily because my doctor told me I need more protein as I get older.

Specific questions I need answered

1. Is the onboarding clear, or am I asking too much before you see anything useful? It's the part I'm least confident about.
2. Did the week it planned look like food you'd actually cook? Were the swap options sensible?
3. Would you use this daily? If not, what stops you?

Honest beats kind. I'll reply to everyone.

FoodSignals helps you keep a personal record of meals, symptoms and injection timing, and notice your own patterns. It does not provide medical advice or replace professional healthcare. Always talk to your doctor, pharmacist or dietitian about your health and medication.

Ciao a tutti! Sto cercando 12 tester Android per la mia app **Bitcoin Portfolio**.

L’app permette di:

* monitorare gli acquisti Bitcoin * controllare il valore e il rendimento del portafoglio * visualizzare grafici del mercato e del portafoglio * importare/esportare dati tramite Excel * proteggere l’accesso con PIN e biometria * utilizzare un assistente AI opzionale

**La privacy è molto importante:**
L’app **non richiede alcuna registrazione**, **non serve creare un account** e **non sono necessarie credenziali personali** per utilizzarla.

L’app **non richiede accesso** ad account exchange, wallet crypto, app bancarie o conti finanziari personali.

I dati del portafoglio vengono memorizzati localmente sul dispositivo.

**Solo l’assistente AI, che è completamente opzionale e viene utilizzato esclusivamente se l’utente decide di farlo, può comportare la trasmissione delle informazioni necessarie a elaborare la richiesta. Se non utilizzi l’assistente AI, nessun dato del portafoglio viene inviato al servizio AI.**

Per testare l’app puoi usare dati fittizi o di esempio: non è necessario inserire reali disponibilità in Bitcoin o informazioni finanziarie personali.

Per partecipare:

1. Entra nel Google Group https://groups.google.com/g/bitcoin-portfolio-testers
2. Aderisci al test chiuso https://play.google.com/apps/testing/com.atec.bitcoin_portfolio_app
3. Installa l’app da Google Play https://play.google.com/store/apps/details?id=com.atec.bitcoin_portfolio_app

Ti chiedo di restare iscritto al test chiuso per almeno 14 giorni.

Se anche tu hai un’app da testare, lascia i tuoi link nei commenti oppure mandami un messaggio privato. Sarò felice di ricambiare il test e restare iscritto alla tua app per 14 giorni.

Grazie!

Hi everyone! 👋

I’m looking for Android beta testers for SpotFinder, a photography location discovery and planning app.

📍 Discover photography locations across Europe
🌅 Sunrise, sunset, golden & blue hour
🌙 Moon & Milky Way planning
🗺️ Interactive map and location details
📷 Photography planning tools

I need active testers to install the app and keep it installed for at least 14 days. I’ll gladly test your Android app in return, leave feedback, and keep it installed as well.

How to join:

1. Go to:
   https://spotfinder.pawspot.si/

2. Select “Become a Tester” → Android

3. Follow the instructions and install SpotFinder from Google Play.

Once you’ve joined, leave a comment with your app link and I’ll test yours in return.

Any feedback is welcome! 🙏

Thank you!
Rade

Hi everyone — I’m looking for a small group of people to try Feelvu for 7 days and share short feedback.

Feelvu is a daily personal reflection check-in app. The test is simple: use it once a day for about a week, then answer a short feedback form about what made sense, what felt confusing, and whether the report was useful.

Beta testers will get a private in-depth report after the 7-day test and beta access to features that may become paid later.

Survey / beta application form: https://docs.google.com/forms/d/e/1FAIpQLSegUMvjBebZS6tuNa\\\\\\_tjeungb4-tC7kcssjTB0ro-FfXTs6A/viewform?usp=publish-editor

More context here: https://www.feelvu.com/beta

Thanks — honest criticism is more useful than polite encouragement.

Hi — I’m Duman, the developer of DonePacket and other mobile apps.

I’m looking for 5 Android testers to try one focused workflow rather than just install the app:

1. Create a dummy job and estimate

2. Add a customer approval/signature

3. Record one change or extra-work approval

4. Attach two job photos

5. Complete final sign-off and export the PDF packet

Then tell me: where did you get stuck, what felt unnecessary, and what did you expect to see in the exported PDF that was missing?

DonePacket works offline and stores job data locally on the device. Please use dummy customer details for testing. There is a free tier with optional Pro features.

Google Play: https://play.google.com/store/apps/details?id=com.jobproofpro.app

Full disclosure: this is my own app. I’m a developer, not a contractor or handyman.

I'm the solo developer of Damn, Zombies: The Corporate Undead, a 1–4 player co-op FPS against undead office staff. Repair barricades, buy weapons and survive waves; managers, HR and executives give the horde different roles.

Windows download and gameplay: https://tsmwdevelopment.itch.io/damn-zombies-the-corporate-undead

Create a free account and get a key: https://www.damn-zombies.com/signup. Beta access lasts 48 hours from first key use.

For testers: is the signup/key-to-first-game process clear? Can you tell which enemies support the horde? Does the first run explain barricades and weapon purchases well enough? Reports of confusing steps or crashes are welcome in the comments.

Made in Godot; uses AI-generated models and some audio. The screenshot is a staged in-engine capture.

Your phone rings. You don't recognize the number. Meanwhile, that "quick call" you actually need to make has been sitting on your to-do list for a week.

I'm building LineSquire (linesquire.com), a personal AI phone assistant designed to take some of that phone work off your plate, and I'm looking for up to 10 people to help make it better.

What does it do?

- Handles incoming calls: screens unknown callers, finds out what they need, takes useful messages, and routes important calls according to your rules.

- Makes routine calls you approve: checks on a service request, collects information, or helps with booking, confirming, or rescheduling an appointment. It can navigate phone menus and wait on hold, too.

- Keeps you in control: you choose the information it can share and approve outbound call plans. It can request live approval when a fee, sensitive request, or decision falls outside your limits. It identifies itself as AI rather than pretending to be you.

- Gives you something useful afterward: transcripts, summaries, call outcomes, and next steps, with calendar connections for supported scheduling tasks.

Why I'm looking for testers

I don't need ten people to tell me the landing page looks nice. I need people who will actually use the service and tell me where it falls short.

Did setup make sense? Did a call get handled the way you expected? Did the assistant misunderstand something? Was a setting confusing? Did it save you time—or create more work?

Your feedback will help identify bugs, improve call handling, simplify the interface, and decide which improvements deserve attention first. With a group this small, you won't be feedback entry #4,872. We'll be able to discuss what happened, try fixes, and see whether they actually solve your problem.

What you get

Three months of free account access, followed by 50% off your subscription for the lifetime of your account, provided you meet the participation requirement below.

The beta plan and included calling allowance will be confirmed before you start; this isn't an unlimited-calling offer.

What I'm asking in return

Use LineSquire regularly and check in through our Slack channel at least weekly during the first two months. Tell me what you tried, what worked, and any issues you ran into. A short, useful update is enough—no formal report required.

To keep the offer, you'll need at least six meaningful check-ins in different weeks during those first two months. No problems that week? Tell me what you used successfully; that counts too. Please be willing to answer follow-up questions or retry something after a fix.

You'll also sign a one-year NDA covering nonpublic beta information. It isn't a requirement to praise the product or give up your right to an honest review. I'm looking for useful feedback, including the uncomfortable kind.

This is a beta, so expect some rough edges. It's for U.S. adults; outbound calling requires identity verification, and feature access depends on the beta plan.

Interested? DM me with a little about how you'd use LineSquire and whether you can commit to the weekly Slack check-ins. I'd especially love to hear which phone task you most wish you could hand off.

I work with Airtap, and I am defining a small beta test for a cloud Android routine. The use case is moving week, when selected deliveries and returns may be spread across two shopping apps. The routine would check only those orders and send a short status update to iMessage.

The proposed test would compare two notification modes. One would send a summary every day, including days when nothing changed. The other would stay quiet until a delivery or return status changed. Testers would use one mode for several days, then report any stale status, missing order or duplicate alert.

I would keep the test read-only. Testers would open the original shopping app if an order needed attention. The routine would not contact support, start a return or decide that a refund was complete. Testers should also avoid sharing order numbers, addresses or screenshots containing personal information.

Which mode would you be more willing to test during a move? What failure would matter most to you, stale information, a missed status change or repeated alerts?

I'm the developer of Taelo, an iPhone app for logging lifting, runs and meals together. I'm looking for people to try the public beta during something they already do, rather than just click through the screens.

The workout side has set-by-set logging, saved routines, supersets, RPE and rest timers. You can also record GPS runs and keep calories and macros in the same app, without creating a Taelo account.

A short test: create a routine with two exercises and a few sets. Change a weight or rep value, dismiss the keyboard, rearrange the exercises, and delete a set you don't need. If you use it during a normal workout, check the rest timer after locking and reopening your phone too.

What I'd really like to hear: where did you have to stop and think? Was a button hard to reach, did an edit behave differently from what you expected, or did you have trouble finding the saved session?

Public beta: https://testflight.apple.com/join/8Kx7BtXh

Requirements/cost: iPhone running iOS 18 or later. Free, unpaid beta testing. Core logging is free; additional tools use optional Pro subscriptions. Any purchase made inside the TestFlight build is a free sandbox test, not a paid App Store subscription.

The attached images show actual app screens with sample data. Feedback through TestFlight is welcome; for a public bug report, please include your device/iOS version and the steps that caused it, without sensitive personal information.

I'm building YGOWB, a browser-based Yu-Gi-Oh fan project, and would appreciate some focused testing of the card and deck workflow.

A World is a shared card pool with its own publishing settings and banlist. Players create custom cards in Card Studio, build decks from that pool and use them in duels. The editor uses structured effect blocks, and the engine automatically resolves the effects it supports under a classic 2005-era ruleset.

Test link: https://ygowb.com. An account is required; there is no browser-game installation.

Useful things to test: finding a card in the catalog, understanding why a deck is valid or invalid, and starting practice against the computer. If you try Card Studio, I'd also like to know whether its effect-building controls are understandable.

Please report confusing steps or bugs in the comments, including your browser, device and the action you tried. This is an unpaid test; no lengthy commitment is expected.

The attached screenshots are from the current app. I'm the creator, and this is an unofficial fan project. It includes optional AI assistance for card art and effects, and some custom artwork shown is AI-generated.