hey Jamie, I just received a notification from F5Bot about you mentioning Squeaky on HN (I'm one of the cofounders) and thought I'm come and say hello ヽ(∀ )ﾉ
We are indeed cookieless, and don't use IP-based tracking either, though we do screen IPs if you're using our IP-screening functionality to keep your teams internal data out of your analytics (optional). We also suppress data capture of sensitive data client-side by default, particularly helpful to ensure session recordings don't accidentally scoop up personally identifiable text-based data, and there are lots of other ways to fine-tune which data you do and don't want to capture.
If you'd like a demo some time feel free to get in touch via [email protected] :) Also happy to chat about alternatives and their pros and cons, the privacy-first analytics space is heating up nowadays!
Been watching these videos for several months now, pretty relaxing to watch and fascinating too. I feel like this is the BMW equivalent: https://www.youtube.com/@M539Restorations
We don't mention this in the article, but we're a 2 man team and we've bootstrapped the product part-time around our day jobs, though I've recently taken a few months off to focus on it full time - there's a long way to go and lots to learn, but it's been a fun year :)
We capture browser version in Squeaky analytics at the moment, but we don't surface it cause nobody ever asked for it haha. If you want to try/use it I'm happy to visualise it for you!
This book was really important for me early in my career, and I still recommend it to others quite regularly https://www.goodreads.com/book/show/9039673-undercover-user-... it will give you plenty of tactics you can use to conduct user research and gather feedback when you have no users or low budget etc.
I think Clubhouse was perhaps another VC pump and dump. Not necessarily deliberate, but that general flavour of startup that investors hoped to massive inflate and grab market share, with the expectation that there is some early mover advantage to be had in a new category. But because they were only manufacturing demand, rather than creating something people really wanted, it's just not worked out.
Sorry, client-side was not in fact accurate: We check the incoming IP address against a list of blacklisted IP addresses stored for a site before upgrading the WebSocket connection
Ah thanks, we updated all the tabs 2 days ago and some of the empty state links must have been missed! Just pushed up a fix for this now, good catch :)
There's also a feedback item in the nav if you catch any other things, and do let me know if you'd like a demo or any other help getting started ( *・∀・)ノ゛
Hi wingerlang, sorry about that, it should have said web app on the homepage - I've updated it now! I've tried to say web app all the time in the app but forgot on the homepage, where it's arguably most important :(
Mobile session capture is technically possible using the approach we're using i.e. not screen recording but just tracking events and DOM changes and they rebuilding that. We looked into it but it was out of scope for now as we're just a two person team. Fullstory already solve for mobile, as do a few other competitors, perhaps you can find out a little from googling their approach?
In terms of privacy, for the web we can mask form inputs by default, and otherwise you can just add tags to elements you don't want to track and then the script ignores them client-side.
yes definitely, we really liked that feature in fullstory, also noticed it in some competitors too. We have it in our roadmap, though it's not until next year some point :( It's clearly something that will be super valuable to people though!
oh haha, nice catch, I've updated it with the correct copy now! No idea how I didn't spot that :(
If you would like a demo of Squeaky then let me know, there's a demo booking page on the website - I'd also be really interested to learn about Microsoft Clarity from you too :)
They invited me for a job interview for a Principle Designer role out of the blue (i.e. I didn't apply). I was really excited cause I loved the company and had lots of ideas how it could be improved. Anyway, ultimately they felt there were 'more data driven candidates'. I respect that, they know their business better than I do, but I still was really excited about some of the opportunities in the user analytics space and I learned some really valuable stuff in the interview that gave me the motivation (along with the rejection) to go and solve the problem for people :)
I have actually written a short blog post about it if you're interested I can share a link.
Pricing-wise, currently it's free, and we'll make sure there's a full-featured free tier if/when we introduce paid plans. The current plan is the have usage-based pricing i.e. a certain amount of sessions per month, but we'll be surveying our users to set appropriate tiers and price points :)
We experimented with live sessions but weren't happy it was real-time enough to be more meaningful than after a short time delay, it's in our backlog to revisit when we can spend time on performance though!
At the moment it's not set to be triggered for specific sessions, none of our early users have requested that but it would be pretty easy for us to implement :) At the moment we're letting our most engaged users take a very active role in determining what comes next e.g. we rolled out IP screening (all happens client-side) and email/domain name screening yesterday as per a request we received yesterday morning. If you sign up we could get triggered recordings in for you super fast ;)
No open API access, we have discussed it though. Recording link sharing with private, or public links, and mp4 and gif (snippets) export is next up.
Sounds like you're a FullStory user at the moment, which features do you currently get the most value from?