3 ms·
I can't speak as to what generally makes a good tech demo, but I can say that as a JS dev, I looked at your website, watched the video a few times, and still ca
by solardev 4y ago
I can't speak as to what generally makes a good tech demo, but I can say that as a JS dev, I looked at your website, watched the video a few times, and still can't figure out how your product is different from the built-in debugger in IntelliJ and VSCode.
You say "time travel", but unless I missed it, your demo keeps going forward in time, stepping through breakpoints. Any debugger can do that.
The interesting part here is the time travel, but I don't see it happening. What does the back arrow do? What happens to a previous state if a future line of code changes it? What happens when you step backwards through a loop or recursion? I think I envisioned something like the time-travel in the Redux devtools extension, but I don't see that.
Your front page has a lot of words but a pretty low signal-to-noise ratio. Instead of long paragraphs of fluffy text, followed by a rambly video, can you show it in a simple animation or two? Kinda like this: https://tailwindcss.com/ https://tailwindcss.com/ If you can make it an interactive actual demo, that would be even better (even if you faked it and all you could do is push back/forward and not edit the code or breakpoints).
For example, it can show what a basic ecommerce product page, or controlled SVG graphic, or anything... what would stepping forward and backward do? Also, how does it work (or not) with my existing repo/framework/toolchain/IDE? Does it only work for simple single-file scripts, or can I integrate it into my existing complex project (the kind that would actually warrant a debugger)?
I don't know if your product is meant to be targeted towards dev end-users, or whether you want to team up with Codesandbox/Codepen or the like to integrate directly into their web editors. But if it's meant to be targeted to devs directly, I just don't have enough information to make a judgment on what it does, how it works, and if it's worth trying out.
Focus on your differentiating features... show us the magic of time travel, not how a basic breakpoint works.
Edited to add: We don't want long-winded stories. Every week, we already spend hours evaluating a million NPM packages and JS tools and frameworks... you have like 5-10 seconds to convince someone that you actually made something useful and novel. Use that time and space wisely, above the fold and in simple, easy to understand bullet points or graphics/animations. Save the long copy and detailed videos for detailed pages that you drill into.
- bluelightning2k 4y agoThank you - excellent feedback. At first I read it as slightly harsh, but once I put aside my ego and really appreciate the feedback. Really excellently put. FWIW stepping through the breakpoints can go forwards AND backwards, and it's embeddable within FAAS environments like Lambda which don't have the debugger available. It uses clever compilation to emulate it in impossible places. And it's 100% on me that I didn't put this in the site ^. Thanks again.
- solardev 4y agoHey, thank you for reading, and I apologize for that! It was not my intent to sound harsh, but I can see how it would come across as such. I meed to work on my online tone, and that's on me. Please don't feel disheartened by that! I am genuinely curious about your service and I think it's really cool. I hope you find a way to showcase it even better, because I get the feeling it's made of some serious programming magic™ :)