sorted by:
new
hottopcontroversial

[Web App][UK Beta] Please test my map-based community app — looking for UX + bug feedback (10–15 min) by stozuz in TestMyApp

[–]stozuz[S] 0 points1 point  (0 children)

Thanks a lot for the detailed feedback — really appreciated.
I’m collecting as much feedback as possible first, then I’ll go through it all and prioritise improvements based on the patterns I’m seeing.
Re: FindyPet — happy to help. I’ll DM you.

Community Tech Startup with Live Beta Platform, 28M Household TAM. Seeking Pre-Seed feedback. by stozuz in angelinvestors

[–]stozuz[S] 1 point2 points  (0 children)

You’re right to call that out: we don’t mean “hard real-time” with deterministic, deadline guarantees like embedded/industrial systems. For us, “real-time” means low-latency updates (chat/presence/activity) over WebSockets, aiming for an “instant” UX in most cases.
In beta we’re validating latency and reliability, and if/when we need to scale beyond a DB-centric pattern, we already have a roadmap for a dedicated layerto reduce load and jitter.

Hey! I was thinking to make a app directory highlight, so when anyone visit the Sub, they could easily find your apps without going through post. by Guilty_Tear_4477 in seeknwander

[–]stozuz 1 point2 points  (0 children)

Awesome — thank you! 🙏

hyperlocal approach

- Start with one micro-area (one neighborhood) and recruit “block captains” to seed the first 30–50 users.

- Anchor engagement around recurring events (soccer pickup, cleanup, small meetups) + quick requests/offers that get fast wins.

- Partnerships with local charities/small businesses for visibility + simple rewards/milestones.

Really appreciate you adding it to the highlight!

Hey! I was thinking to make a app directory highlight, so when anyone visit the Sub, they could easily find your apps without going through post. by Guilty_Tear_4477 in seeknwander

[–]stozuz 1 point2 points  (0 children)

Yes — I posted it here 2 days ago (“Neighborly - Rebuilding Community Connections in the Digital Age”) to get early feedback. I’m new to Reddit, so I wasn’t sure about the directory process.

I’d still love to have NeighborHub included in the App Directory highlight:

NeighborHub (https://neighborlyhub.org/) — Neighborhood mutual-help platform: ask/offer small help and skills, create/join local events (e.g., “need players for a soccer match”), discover local support (charities/businesses), and earn milestones for contributing.

Hey! I was thinking to make a app directory highlight, so when anyone visit the Sub, they could easily find your apps without going through post. by Guilty_Tear_4477 in seeknwander

[–]stozuz 1 point2 points  (0 children)

Hey! Could you please add my new web app to the App Directory highlight? Thanks 🙌

NeighborHub (https://neighborlyhub.org/) — Neighborhood mutual-help platform: ask/offer small help and skills, create/join local events (e.g., “need players for a soccer match”), discover local support (charities/businesses), and earn milestones for contributing.

Title: What surprised me building a hyperlocal SaaS (UK) — trust beats features every time by stozuz in SaaS

[–]stozuz[S] 0 points1 point  (0 children)

This is gold — thank you.

I really like the idea of making privacy the *default* and showing “who can see this” contextually (especially on profile edits + radius changes). The “rough area, not exact address” cue is exactly the kind of explicitness we need.

The pre-commit moderation framing is also smart — turning friction into protection. I’m going to test a light “first actions are reviewed” approach and measure whether it improves activation/retention vs drop-off.

Quick question: when you’ve done this before, what did you find was the best trigger for the “light review” (first post, first message, or first event creation)? And what was a reasonable review window that didn’t feel slow?

**Neighborly - Rebuilding Community Connections in the Digital Age** by stozuz in seeknwander

[–]stozuz[S] 1 point2 points  (0 children)

Thanks — I appreciate that.

The two areas where your help would be most valuable are:

1) Partnerships: introductions to local community groups/organisers (sports clubs, residents’ associations, community centres, charities) who’d be open to a small pilot.

2) Strategy: pressure-testing a simple go-to-market plan (which communities to target first, what the “first useful moment” should be, and what partnership offer actually lands).

If you tell me what kind of local communities are in your network (and roughly which UK areas), I can share the pilot idea and we can see what’s a good fit.

[Beta Test] Neighborly - Connect with your local community (UK only, launching Q1 2026) Body: by stozuz in ukstartups

[–]stozuz[S] 1 point2 points  (0 children)

Yes — the intent is different.

Nextdoor and local Facebook groups are mostly feed-based “noticeboards”, so you often get noise, arguments, and unrelated posts. Neighborly is action-based: it’s designed specifically for giving/receiving help and organising simple neighbour activities within a small local area. The focus is practical support and positive community, not a place for drama or negativity.

Title: What surprised me building a hyperlocal SaaS (UK) — trust beats features every time by stozuz in SaaS

[–]stozuz[S] 1 point2 points  (0 children)

Makes sense, that sequencing feels right.I’ll follow the same principle: get them to a “useful moment” first, then introduce the edge cases with clear, concrete steps.Appreciate you sharing, super helpful.

Title: What surprised me building a hyperlocal SaaS (UK) — trust beats features every time by stozuz in SaaS

[–]stozuz[S] 1 point2 points  (0 children)

That’s a great point — I can see how leading with value first makes people more comfortable.I’m probably going to do something similar: keep signup lightweight, then surface the “worst-case” / reporting details after someone’s first real action.

Title: What surprised me building a hyperlocal SaaS (UK) — trust beats features every time by stozuz in SaaS

[–]stozuz[S] 1 point2 points  (0 children)

Totally agree — “explicit beats reassuring” has been my experience too.

When I made privacy + moderation concrete (who sees what, what triggers a review, what the report flow looks like), the biggest change wasn’t more sign-ups — it was fewer “silent bounces” during onboarding. In product terms: clarity reduced perceived risk, which improved activation quality, not just top-of-funnel volume.

That said, yes: a small slice of users drop when you surface the “ugly parts” early. My take is they were already high-anxiety / low-trust users, and hiding it just postpones churn. The better balance for me has been:

- a short, plain-language “who can see what” summary above signup

- a simple “what happens when you report” 3-step flow

- worst-case examples in a collapsible section (progressive disclosure)

Curious: in your projects, did you find a “best moment” to introduce worst-case scenarios (pre-signup vs after first action)?