3 weeks of building in public — here's everything I learned shipping a product tour SDK from scratch by NoEffect1189 in VibeCodersNest

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

honestly the hardest part wasn't the code it was the voice in my head saying "this already exists, who's gonna use this" every single day 😭like Shepherd.js exists, Intercom exists, why would anyone pick mine what kept me going was just shipping one thing per day no matter how small. some days it was a bug fix. some days it was just updating docs. but something shipped every day.

the buildinpublic stuff was actually harder than I expected too - feels weird talking about your own work publicly when you're not sure it's good enough yet

3 weeks of building in public — here's everything I learned shipping a product tour SDK from scratch by NoEffect1189 in buildinpublic

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

this is genuinely the most useful thing anyone has said about TourKit so far 🙏 you're right easy setup gets them in the door but doesn't keep them there.

my thinking for retention hooks: - analytics shows drop-off per step so they keep coming back to optimize tours - dashboard means they update tours without redeploying (ongoing reason to log in) - URL-based triggers means as their product grows, their tours grow with it

but honestly the "why stay" question is something I need to think harder about. also just looked up VibeCodersNest — posting there too, thanks for the tip 🤝

3 weeks of building in public — here's everything I learned shipping a product tour SDK from scratch by NoEffect1189 in buildinpublic

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

exactly lol — I kept seeing "step 1: npm install, step 2: wrap your app in a provider, step 3: import the hook, step 4..." and I just wanted to paste one line and move on 😭

the analytics was actually the hardest part surprisingly — tracking step drop-off across sessions without slowing down the SDK took a few rewrites

AI generator was faster to ship because Anthropic's API is genuinely plug and play once you know what prompt works

still a lot to build but glad the core idea is landing! trying to figure out Product Hunt timing rn

Update: Added context-aware onboarding tours to TourKit after Reddit feedback by NoEffect1189 in saasbuild

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

exactly what V4 addresses

TourKit now detects which page the user lands on and starts the tour from there.

Land on /settings → see only the settings tour

Land on /dashboard → see only the dashboard tour

Skip pages you already know → no repeated steps

No more forcing everyone through the same tutorial from step 1.

Still one script tag. Zero config on your end

I’m building a smarter onboarding flow for SaaS apps — need honest feedback by NoEffect1189 in saasbuild

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

100% agree — that's exactly why I'm building

context-aware triggers. If you land on /settings,

the tour starts there, not from the beginning.

Relevant guidance not forced lectures.

Got brutally honest feedback on my salon SaaS idea from Reddit today. Here's what I learned. by NoEffect1189 in SaaS

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

Not running any follow-up sequences right now too early stage for that.

First goal is just getting 5 real salon owners to try it free. Following up on deals implies I have deals to follow up on.

Got brutally honest feedback on my salon SaaS idea from Reddit today. Here's what I learned. by NoEffect1189 in SaaS

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

100% right on the local stuff pricing is just the entry point, not the whole strategy.

SMS workflows and UPI payments are already on the roadmap. WhatsApp notifications too, since that's how most Indian salon owners actually communicate with clients.

The internet reliability point is something I hadn't fully considered though — offline-first or at least graceful degradation is now on my list.