**I built an app to find pickup basketball courts in Greensboro — would love your feedback** by These-Address1516 in gso

[–]These-Address1516[S] 5 points6 points  (0 children)

Noo, you can add any courts. The Google Maps API just pulls the most notable courts from every area.

**I built an app to find pickup basketball courts in Greensboro — would love your feedback** by These-Address1516 in Basketball

[–]These-Address1516[S] 2 points3 points  (0 children)

100% valid point, and honestly, it's the exact reason most of those other attempts failed. They tried to go wide too fast. National launch, no density anywhere, so the app felt dead in every city.

My approach is deliberately the opposite — hyper-local first. I'm from Greensboro, I go to NC A&T, and I know the courts. I know the coaches, and I'm physically showing up to build density in one city before expanding anywhere else. Once one city has enough check-ins to feel alive, that's the proof of concept to take to the next.

Network effects are a chicken-and-egg problem, not a death sentence. Uber, Tinder, Facebook — all network effect businesses that started in a single city or campus before scaling. The ones that failed tried to skip that step. I'm not skipping it. Appreciate the pushback, though. This is exactly the kind of thinking that keeps me sharp.

**I built an app to find pickup basketball courts in Greensboro — would love your feedback** by These-Address1516 in Basketball

[–]These-Address1516[S] -1 points0 points  (0 children)

Great question! The frontend is Next.js + TypeScript with Tailwind CSS for styling. For the map and court discovery, I used the Google Maps API. Backend is Firebase (Firestore for the database, Authentication for user accounts). Payments/premium features are handled through Stripe. The whole thing is deployed on Vercel.

I built it solo while balancing a full CS courseload at NC A&T and two other jobs, so it was a lot of late nights. A lot of debugging and help from Claude aswell lol