this is pretty slick! I like how the entire interface is SMS based
59 karma · joined October 10, 2011
What do you mean by "Backend-as-a-service"? Tell me more.
Also I use FK to monitor our existing features and ask feedback on them. I love that now i don't have to write 4 lines of code to monitor 1 line of code. FeatureKicker's no-change solution to monitor and get feedback on existing features rocks.
I think this seems like an "easy" thing to build in-house, but we believe getting this right will take a ton of time, which companies could put towards doing what they do best.
Here is what we have: 1. The rules engine, to track visitors and fine control who see's feature experiments and how often. 2. An analytics suite, to capture all data and show it in a form which is digestible and allows a PM to take action 3. Making overlays work cross browser and device. 4. Solution which requires absolutely no-code to get feedback on existing features. A gui where PM's can visually find features on their website, tap on them and configure them to ask for feedback.
We have a rules engine, which can be used to really fine tune when and how the feature experiments are shown.
For example, you can setup so 1. feature experiments are only shown to a customer who has logged in at at least X times. 2. You can control so they don't see an experiment after it has been seen once by them. 3. You could say that if they have seen 1 feature experiment, then they shouldn't see another 1 for X days. 4. You could also only show to X percentage of your traffic. 5. And many more rules.
I like the idea of being able to crowd source ideas. It would be a great feature for me to "kick" and see what customers say :)
We think this is because we ask the right person, the right question at the right time. Its the right person, because this person clicked on the feature, its the right question because the question is about the feature they clicked on and not their age, gender etc. and its the right time because they are in the app, just clicked on the feature and at the height of their curiosity when it comes to that feature.
In regards to frustration, we believe this is a valid theoretical concern, but in practicality with our 27 beta customers, we haven't yet had anyone complain.
We think this is because our customers are using this in a "logged-in" product, leveraging our rules engine to control how often the feature experiment is shown and to who.