I am building a B2B product for engineering teams and trying to decide whether to start with SMBs or pursue larger companies from day one.
Larger organizations may have stronger budgets, but they often already use internal tools and have longer sales cycles. Smaller companies seem easier to reach and more likely to feel the problem, but I m concerned that optimizing for early SMB customers could pull the product away from the enterprise market.
Would you use SMB sales mainly for customer discovery and early traction, then move upmarket, or define the long-term ICP before building further?
Never came across this one before, maybe it is new now due to Forums ?
Sometimes, when Im providing feedback to a product launch, or when Im replying to someone's new thread I cannot reply. it usually happens after then first couple of comments I make. I try to reply to someone's response and I get "invalid content detected". Anyone facing this issue? is there a way to fix?
I recently built a fairly complex mobile app without operating a traditional backend. Originally, the decision was about cost. I didn t want to pay for servers before knowing whether people would actually use the product. That constraint forced me to rethink several things I would normally send to an API. Reading progress, bookmarks, highlights and settings are stored locally. File processing happens on the device. Backups go directly to storage controlled by the user. Even nearby file sharing temporarily turns the phone into a small local server. The unexpected result was that the app became more private, more reliable offline and less dependent on third-party infrastructure. The trade-off was development complexity. Background processing, local file conversion, device-to-device sharing and data recovery all required more work than simply sending everything to a server. I still think backends are necessary for collaboration, social features, server-side secrets, centralised accounts and real-time synchronisation. But now I ask a different question before adding one: What specific product requirement makes the server necessary? For other mobile developers here, what feature usually becomes your tipping point for introducing a backend?
Hey everyone! I m a newcomer here, and I ve built 3 apps so far. However, I m struggling to determine the most effective strategy for marketing them. Any insights or suggestions?
A questionnaire web app requires a solid online database. I started off with a combination of Vercel and Neon for frontend and backend, but one of them required GitHub to be involved. This kinda complicated things because to make it work, stuff had to be done in all three and that didn't't always work well. Changes here required more changes somewhere else and that dance continued until a partial reset became necessary. However, by then the whole thing had become such a mess that a complete reset was the only reasonable way out.
Now I have to admit that I was not saving every step on GitHub, but there was a good reason for that. There were so many different edge functions and functionalities required that even with GitHub it would have been hard to keep track, especially since GitHub itself was part of the mess. Instead of a reset I ended up switching to a combination of Netlify and Supabase and the problems we faced there were product design issues, not software functionality.
Went through my notifications today and found what looked like two separate unanswered messages from the same person on the same thread. Both showed up in the notification list looking equally new.
Opened the actual thread instead of trusting the list, and one of the two already had my reply sitting under it from a few hours earlier. The notification just never went away after I answered it.
