u/Emeric_MidlyCertain

Looking for UX feedback on a 14-day Android closed test

Hi Inventory Managers!

I’m running a 14-day Android closed test for a small mobile app I’m building, and I’m looking for practical feedback, not promotion.

The app is a simple inventory tool for small retailers: scan a barcode, create or find a product, record stock in / stock out / adjustments, and keep a basic inventory history.

I’m mainly trying to validate whether the flow is clear enough for someone who has never seen the app before.

What I’d like feedback on:

  1. Is the onboarding clear, or does it feel confusing?
  2. Does the scan-first workflow make sense?
  3. Are the stock actions easy to understand?
  4. Is anything visually unclear, slow, or annoying?
  5. Would you trust this app enough to test it with dummy inventory data?
  6. What would make you uninstall it in the first 5 minutes?

A bit of builder context: I built the app solo. I’m not a professional developer, but I like coding, and this is my second AI-assisted software project.

I’ve had to deal with inventory management in several of my jobs: as a retailer and ecommerce operator, and also as the CFO of an organization where my team struggled to keep stock up to date in a simple, reliable way.

My app is based on problems I’ve personally experienced, and also on what I saw in other apps that felt either too complex or too expensive.

So I’m trying to find out whether I’m solving a problem that is broader than my own use case.

For the tech part: It’s built with React Native + Expo, with Supabase and RevenueCat. It already supports English, French, and Spanish.

I do have a roadmap, but before adding more features, I’d like to learn from actual users in my Ideal Customer Profil: small retailers, makers, or craftspeople who manage supplies, products, or small inventories.

I’ve been working on it for about 2 - 3 weeks using a spec-driven development workflow with Codex. I tried to put serious effort into project documentation, tests, and security. My weakest point is probably design, so UX/UI feedback would be especially helpful.

Happy to share more about the build process if that’s useful to anyone here.

This is Android only for now. You do not need to be in retail to help, but feedback from founders, indie app builders, Shopify / ecommerce people, or anyone who has dealt with inventory would be especially useful.

No payment, no pitch, and nothing to buy now or later. I’m just trying to get real testers, collect honest feedback, and go through the closed testing process properly.

Closed test link:
I don’t want to break the self-promotion rules. Is it okay to share the Google Play closed testing link here, or should I only send it by DM to people who ask?

reddit.com
u/Emeric_MidlyCertain — 13 hours ago
▲ 2 r/AppBusiness+1 crossposts

Looking for practical feedback on a 14-day Android closed test: barcode inventory app

Hi r/AppBusiness!

I’m running a 14-day Android closed test for a small mobile app I’m building and I’m looking for practical feedback, not promotion.

The app is a simple inventory tool for small retailers: scan a barcode, create or find a product, record stock in / stock out / adjustments, and keep a basic inventory history.

I’m mainly trying to validate whether the flow is clear enough for someone who has never seen the app before.

What I’d like feedback on:

  1. Is the onboarding clear, or does it feel confusing?
  2. Does the scan-first workflow make sense?
  3. Are the stock actions easy to understand?
  4. Is anything visually unclear, slow, or annoying?
  5. Would you trust this app enough to test it with dummy inventory data?
  6. What would make you uninstall it in the first 5 minutes?

This is Android only for now. You do not need to be in retail to help, but feedback from founders, indie app builders, Shopify / ecommerce people, or anyone who has dealt with inventory would be especially useful.

No payment, no pitch, and nothing to buy now or later. I’m just trying to get real testers, collect honest feedback, and go through the closed testing process properly.

Closed test link:

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

If this belongs in the Friday feedback thread instead, I’m happy to move it there.

[Edit before 1st comment]
A bit of builder context: I built the app solo. I’m not a professional developer, but I like coding, and this is my second AI-assisted software project.

It’s built with React Native + Expo, with Supabase and RevenueCat. It already supports English, French, and Spanish.

I do have a roadmap, but before adding more features, I’d like to learn from actual users in my ICP: small retailers, makers, or craftspeople who manage supplies, products, or small inventories.

I’ve been working on it for about 2–3 weeks using a spec-driven development workflow with Codex. I tried to put serious effort into project documentation, tests, and security. My weakest point is probably design, so UX/UI feedback would be especially helpful.

Happy to share more about the build process if that’s useful to anyone here.

reddit.com
u/Emeric_MidlyCertain — 13 hours ago

Hey everyone,

I’m getting ready to release my first Android app, and I just found out Google requires closed testing before publishing on the Play Store apparently with at least 12 testers.

I still have a few UX improvements and some Play Console setup to finish, but I’m trying to understand how people usually find testers for this stage and how did you manage that on your side?

Is it allowed on Reddit (r/AppBusiness for example or another?) to create a post asking for testers and share the Play Store testing link? If yes, which subreddits are the most appropriate for that?

My app is focused on business inventory management, so unfortunately my close circle probably won’t be very interested or useful as testers.

Would appreciate any advice or feedback from people who already went through this process.

reddit.com
u/Emeric_MidlyCertain — 6 days ago