Platform Building 214 Dec 2017
tldr - week2. posted on Indie Hackers. deciding on success metrics.
What I did
Last week I pushed out the UI updates and added a feature enabling users to see past package releases. Looking at the time I spent, I think I’ll need to plan for two 2hr sessions on python toolbox a week to continue building it out.
I also ran my platform idea by the indiehackers.com crowd. In this (IH thread)[https://www.indiehackers.com/forum/has-anyone-stolen-or-out-hustled-you-once-you-posted-your-idea-here-bdf22b7984], I asked if anyone has stolen and out-hustled someone on an idea (I wondered if getting feedback would be risky). Once satisfied I wasn’t risking anything, I posted a form of my idea in this (IH thread)[https://www.indiehackers.com/forum/aggregator-sites-started-one-how-to-do-one-well-8a49680d3c]. Two people commented on getting an invalid SSL cert (it was expired). No other feedback.
- (1) removing little roadblocks is super important when asking for general internet feedback
- (2) it’s probably safe to share an idea with the world - they really only care about it after it’s built.
Priorities for this week
I checked Google Analytics and found that something like 8 people visited to site looking at the pandas package. I need to decide on success metrics for when people come in from google vs come from the Python Toolbox home page.
And honestly, I really haven’t decided specific actions that the site is supposed to help users with. Yes, it has info on python releases, but how is that info valuable to users? I’d love to ask that question to users live on the site. That’s the focus of this week.
So in a distilled version,
- decide on success metrics for users from Google
- figure out how to ask questions on the site