Landingpage says „starts at 30$“, pricing page lists „from 75$“ - quite confusing tbh.
Launch HN: 1Flow (YC W22) – In-product user feedback for web/mobile apps
21–30 of 66 posts
Re: Launch HN: 1Flow (YC W22) – In-product user feedback for web/mobile apps
#22This is gimmicky and intrusive to the users. How is this any different from the other 999 solutions that do the same thing?
I think you're right in pointing out this shouldn't be done without respect to the users. What we're seeing is that many users who interact with our widgets actually appreciate this - they would recommend the app they're using and tell us they recommended the app because they felt important and their opinions valued. You're 100% right that some folks might not want to interact with this and we've optimized our UX such that users who don't want to interact with this, don't need to at all. I wrote detailed answers to why we're different in the original post, so I'd be happy to hear your thoughts on what you think on these points! :)
Re: Launch HN: 1Flow (YC W22) – In-product user feedback for web/mobile apps
#23I was looking at pricing. What is a "tracked user"? I'd be more inclined to pay for a certain number of survey responses. Typeform's model of scaling price with # of responses seems in line with 1Flow's value.
A tracked user is anyone who opens your app. Yeah with people who are familiar with survey tools we've heard similar feedback as what you said. The reason we're currently pricing it based on MTUs is because we actually track what users do (i.e. events and sessions) in the background, and give you the option of targeting any specific user cohort anywhere in their user flow to get the most relevant and contextual feedb…
How do you count users from the EU who send „do not track“ requests via their browser? It would actually be illegal for you to track them - would they count?
Re: Launch HN: 1Flow (YC W22) – In-product user feedback for web/mobile apps
#24Landingpage says „starts at 30$“, pricing page lists „from 75$“ - quite confusing tbh.
Oh nice catch! Corrected this and deployed - sorry about that! it's free to setup & test and our pricing starts at $75/mo for up to 10k monthly users.
Re: Launch HN: 1Flow (YC W22) – In-product user feedback for web/mobile apps
#25Earlier quoted context omitted.
A tracked user is anyone who opens your app. Yeah with people who are familiar with survey tools we've heard similar feedback as what you said. The reason we're currently pricing it based on MTUs is because we actually track what users do (i.e. events and sessions) in the background, and give you the option of targeting any specific user cohort anywhere in their user flow to get the most relevant and contextual feedb…
How do you count users from the EU who send „do not track“ requests via their browser? It would actually be illegal for you to track them - would they count?
No they wouldn't count. We need to explain this better in our docs so thank you for bringing this up, it's on my to-do list now. Oh, btw we do not use cookies so if your site didn't need cookie notices before, you won't need them after adding 1flow.
Re: Launch HN: 1Flow (YC W22) – In-product user feedback for web/mobile apps
#26Earlier quoted context omitted.
How do you count users from the EU who send „do not track“ requests via their browser? It would actually be illegal for you to track them - would they count?
No they wouldn't count. We need to explain this better in our docs so thank you for bringing this up, it's on my to-do list now. Oh, btw we do not use cookies so if your site didn't need cookie notices before, you won't need them after adding 1flow.
Thank you for the reply!
Not to be nitpicking, but it’s not (only) the cookie that requires consent, but the storage and the use of the data itself. So if your customers do not have a cookie consent yet, they might even have _more_ work to do to implement your solution because they still have to ask for permission and store the answer.
Re: Launch HN: 1Flow (YC W22) – In-product user feedback for web/mobile apps
#27This is great! When I design a product I always make sure that it has a built-in feedback/bug reporting mechanism because I know that as a user I hate searching their website for the link to the page with the email to send feedback, and usually don't. But this takes it to the next level.
Thanks for your encouraging words. "The key to scaling is finding bottlenecks before your users do" - I really resonate with this (I saw your talk in 2019) and we're helping companies solve the bottleneck with scaling user feedback. If you or someone else you know would benefit from using our solution, we'd love to chat!
> I really resonate with this (I saw your talk in 2019)
> If you or someone else you know would benefit from using our solution, we'd love to chat!
I'm messaging you right now!
Re: Launch HN: 1Flow (YC W22) – In-product user feedback for web/mobile apps
#28Earlier quoted context omitted.
No they wouldn't count. We need to explain this better in our docs so thank you for bringing this up, it's on my to-do list now. Oh, btw we do not use cookies so if your site didn't need cookie notices before, you won't need them after adding 1flow.
Thank you for the reply! Not to be nitpicking, but it’s not (only) the cookie that requires consent, but the storage and the use of the data itself. So if your customers do not have a cookie consent yet, they might even have _more_ work to do to implement your solution because they still have to ask for permission and store the answer.
For sure this is good feedback! We've planned a feature for explicit user consent at the first interaction, so that our customers who don't already have good privacy practices in place will use our one-click solution.
Re: Launch HN: 1Flow (YC W22) – In-product user feedback for web/mobile apps
#29Congrats on the launch.
Note that higher response rates don't always translate to better data. As you make the survey experience more intrusive you incentivize certain users to provide junk answers simply to remove the barrier. Just something to consider... especially if you decide to scale to enterprise.
Re: Launch HN: 1Flow (YC W22) – In-product user feedback for web/mobile apps
#30Earlier quoted context omitted.
No they wouldn't count. We need to explain this better in our docs so thank you for bringing this up, it's on my to-do list now. Oh, btw we do not use cookies so if your site didn't need cookie notices before, you won't need them after adding 1flow.
Thank you for the reply! Not to be nitpicking, but it’s not (only) the cookie that requires consent, but the storage and the use of the data itself. So if your customers do not have a cookie consent yet, they might even have _more_ work to do to implement your solution because they still have to ask for permission and store the answer.
We believe in a privacy-first internet. We also believe in continuously listening to users efficiently to solve their problems better. I think there's a right way of doing it and we're on a mission to pave the way for all teams building software.