Original Summary

I started golfing last year and ran into a pretty simple problem: I wanted more people to play with. That was basically the original reason I started working on GolfDock. It was supposed to be a relatively simple project around finding golfers and organizing rounds. That did not last very long. As I actually started using it and talking to golfers, the project expanded into GPS, live scoring, stats, leagues, events, leaderboards, friends, round history, watch apps, practice tools and a bunch of things I definitely didn't appreciate the complexity of when I started. Eventually I found myself maintaining: iOS + Android Apple Watch + Wear OS a production backend/database authentication and permissions GPS/course data shared live-round state notifications/deep links a public website and admin systems automated QA across the app, backend and web App Store + Google Play releases I'm a solo founder, so one of the biggest things I've learned is that building features is probably the easiest part of building real software. Getting everything to survive actual users is where it gets interesting. A feature can work perfectly in development and then you discover: two people scoring simultaneously can create a race condition restoring a round after the OS kills the app is completely different from normal navigation QA and production have drifted authentication state changes underneath something a fix works on Android but needs completely different verification on iOS the app works but your automated test is wrong the store build isn't behaving like the local build an apparently tiny feature touches six other systems I've probably learned more from debugging those situations than I did from initially building most of the features. The other big lesson has been not confusing the ability to build something with proof that it should be built. I'm starting to research another completely separate B2B software idea now, and I'm approaching it almost backwards compared with how I originally built GolfDock: find people already experiencing the problem → quantify what the problem costs them → test against their real workflow → only build deeply if they'll actually pay for the result. GolfDock is still actively being developed, but getting it from an idea to an actual production product completely changed how I think about building the next thing. For other solo builders who have shipped something beyond the MVP stage: what was the point where you realized building the product and operating the product were two completely different skills?   submitted by   /u/JakobGolfs [link]   [comments]

  • 情报分类：商业与市场研究
  • 分类依据：内容涉及商业、投资或市场动态
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/9/29 23:34:25