Under the hood it's just a tiny automated email flow set up via Mailchimp that sends out the download link when you sign up. Nothing fancy, but it's easy and it does the job.
I was just about to ask how do you differentiate your product from mitmproxy but on a quick google search I found this thread from a few years ago: https://news.ycombinator.com/item?id=29627819
That said, one point there is outdated: HTTP Toolkit does now fully support websockets too. There's more I'd like to do there, but as far as I'm aware it's equally capable to mitmproxy in that sense today.
For the web dev case, for example, if you're debugging some interaction that means you can intercept your browser <-> server traffic and your server <-> upstream API traffic all in the same place, and see the full flow, and you can modify server responses or backend API responses in flight, to test out different edge cases.
There's a Chrome dev tools vs HTTP Toolkit comparison page here with a little more detail: https://httptoolkit.com/chrome-devtools-alternative/
In a perfect world, I'd kill for a tool where I could define a script (something similar to a Playwright test) and it'd automatically run and record everything, so I could redo the video much more frequently and accurately. I think you probably can do that for a normal web app already (?) but the challenge here is that HTTP Toolkit is launching other apps that also pop up over the top, and so I need to record them all together.
If you're looking for inspiration around this sort of thing, the Android demo video is different and also worth looking at: https://httptoolkit.com/android/
I stumbled on this nice blog post on automating these recordings. Maybe a partial solution?
https://martinheinz.dev/blog/94
I was thinking of doing a manual process like yours for a start rather than automating, but hearing your thoughts makes me think I'll try automating sooner.
I see what you mean about the multi-app aspect. I'll have to switch to browser windows for mine as well. Your android approach is nice!
It's an _extremely_ simple setup. Actual recording is done with Mac's built-in screenshot tool: https://support.apple.com/en-us/HT208721. It's recorded at an arbitrary window size I eyeballed the first time, that now I probably have to stick to forever (because if they're all the same size, I can reuse parts to avoid re-recording unnecessarily).
All of this is suboptimal (using 1080p would have helped, for starters, since lots of tools work better with standard resolutions) but it doesn't really matter, it just annoys me mildly one day a year and that's it.
IMO: if you're at the start, unless you have a super unique situation, I wouldn't look at automating videos or perfecting the recording setup at all - just ship something barely acceptable and see if it works, and then focus on pain points that actually turn out to be blockers later. Getting a core product into real people's hands and getting real feedback ASAP is more valuable than tweaking the video resolution or anything similar!
Like it a lot. Cheers.
I was wondering what the early days of the journey looked like. - What did the first iteration of this product look like? Was it more or less similar, or substantially different from the spirit of httptoolkit today? - How did you go from (some semblance of a product) to first sale? / acquiring first customer? - did you spend anything on marketing/distribution?
Technically, the first iteration was https://github.com/httptoolkit/mockttp - an HTTP integration testing library for JS. Not a desktop app at all! I'd originally built that for testing uses, but as it matured I realised that with a UI and automated setup tools it'd be useful as a complete product (but Mockttp still powers all the internals today, and you can use it directly to build your own custom intercepting proxies too).
For the first real product, the very first public 'launch' was literally a landing page with some demos of the potential UI and a signup form, just to test interest and check it wasn't a terrible idea. The results looked promising, so that was followed a few months later by a very basic but usable free version (entirely read-only, and only supporting Chrome interception) with the freemium features on top appearing a few months after that. From this stage it was all very much the same spirit as today, just less feature complete.
> How did you go from (some semblance of a product) to first sale? / acquiring first customer?
Once I announced the paid version (a blog post to my tiny set of newsletter signups, plus a little response on HN/Reddit/Product Hunt etc) I got a handful of paying customers (but certainly less than 10) within 24 hours. Nice but not a meaningful income, and from that wild peak it dropped back down to maybe one new customer per week or so afterwards, so it was quite slow going at the start.
However, those paying customers (and the mere fact of offering a paid service generally) resulted in _much_ better feedback. Rather than "this is cool" all of a sudden I had real demands for specific features, from people with concrete use cases and money in their hands. The initial paid features were just made up off the top of my head, and honestly didn't create a particularly compelling paid feature set. It's very hard to really know what people will pay for! That feedback was incredibly unbelievably useful to fix that.
From there, building out the key features people asked for over the following 6 months boosted things very significantly, and started to get things moving for real, and then you get into a virtuous circle, where more users => more feedback => better product => more users => ...
> did you spend anything on marketing/distribution?
I tested advertising at a small scale for a few months, but it didn't really work great. I think largely because it's very very freemium - 99% of users pay nothing - so the acquisition cost for a paying user doesn't make sense, and also honestly I don't have much experience with ads and I'm not sure I'm any good at writing them.
Content marketing meanwhile has worked great, keeps passively returning dividends, and cost nothing. I've tried to fill the blog (https://httptoolkit.com/blog/) exclusively with detailed & high-value original content (detailed breakdowns of a recent HTTP security vulnerability, not "top 10 HTTP libraries for Python") which shares well on social networks for an immediate burst of traffic, and then (in most cases) provides both a long-term SEO boost and constant incoming traffic on related topics that converts into users. That starts slow, but again steadily builds up over years, if you keep working at it. Content marketing + SEO are pretty much the only marketing channels I work on right now.
Even with root, certificate pinning can cause problems (as the sibling comment points out) but you can usually defeat that fairly easily: https://httptoolkit.com/blog/frida-certificate-pinning/.
For non-Android, HTTP Toolkit can't set it up for you automatically, but you can absolutely intercept _anything_ manually if you can configure it with your own HTTP proxy setting (fairly common) and add a trusted CA certificate (less common).
Do you mean that improving documentation helped get customers? I have a small side project and I think this is one of its weaker spots, even if it is relatively simple [0]. I noticed "helper popups" are getting used quite extensively.
It probably did, but no that's not what I mean, sorry :-). By "rewriting support" I mean adding features that allowed you to rewrite arbitrary network traffic, rather than just viewing it (as in the very first PoC).
For system-wide setup, you'll just need to configure that manually - setting your system proxy and trusting the CA certificate. The settings you need are on the Intercept page, in the 'Anything' section. For portable browsers, you may also be able to configure proxy & CA settings within the browser itself, which might be more convenient, depending on your setup.
I suspect that'll be a common theme in answers here though: if you have a side project making $2k a month, in most of the world that's enough for you to go full-time and try to take it further. If you can make $2k/month on something working only part-time, you can definitely make a lot more if you focus on it.
On your questions: HTTP Toolkit is a desktop app (plus a mobile app and other components for integrations) but it's an Electron app that effectively functions as a SaaS (with a freemium subscription model) that just happens to have a component that runs on your computer. And actually getting to $2k wasn't overnight at all - it took a couple of years of slow steady slog. A few inflection points that made a notable difference (releasing rewriting support & Android support particularly) but mostly it was a matter of "just keep pushing", trusting the trajectory would keep going, and steadily grinding upwards. It's great where it is now, but it's hard work - a solo business is not for the faint of heart!