Does this landing page explained well what problem I'm trying to solve?
Hey guys, last two month I was working on a side project, here is the landing page https://www.asynctrace.com
I was trying to solve a problem How we can get the full stacktrace regardless the code is synchronous or asynchronous? and how we can remove the framework/3rd party related stacktrace in JavaScript context?
I do believe my product solved those problems! What you guys think ? is the presentation is good enough to move forward? feedback please :)
The landing page looks indeed very informative and to the point. Congrats for shipping!
Might be unsolicited feedback about the product itself, so pardon my intrusion if that's the case and ignore what's next :D
As a long time developer and product owner the use case looks more a fit for a library or a tool I could include in my project to clean up stack traces locally, not a hosted service, and I would feel uncomfortable using it / hard to justify for the higher ups.
I would urge you to reconsider the business model. You don't have to give it out for free, but it has to integrate naturally in the developer workflow. Look at quokka.js for some inspiration maybe.
Otherwise you're in the error management space and you're competing with the likes of Rollbar and Sentry, and you will need to provide a more compelling reason for me (the dev / customer) to upload all my errors to you, than just cleaning up stack traces.
In the case of those services, the sole reason why I would accept uploading errors to them is because it increases visibility of errors happening in a server.
I hope you'll find your perfect niche and wish you the best of luck in your PMF journey!
Thank you very much, I actually like this kind of insightful comment :) Your insight also helps me to understand how other people think about the product itself. And thanks for quokkajs link, I'll check them out.
You brought a few fundamental points, I checked other error trackers. Indeed they are very good at visibility and helpful in terms of what's happening in the production or how the product behaves itself. But in terms of solving bugs (from developers point of view) it might be trickier specially in asynchronous context like async/await, promise, HTTP or RxJs. I didn’t find any other error tracker shed some light on those.
You know, modern frameworks are evolves rapidly, everything considered collection of small components or compound components. The traditional error trackers are still pointing out file based error processing means which file has the error. I’m trying to change the focus to component instead of file so developer can understand which components are most problematic or how many components are involved.
I’ve considered separate view/dashboard for product owners/upper management for the sake of visibility. I’m planning to build a view/graph that would help them to prioritize the bugs and get a holistic view of the product. Most probably they are not interested in stacktraces :P
Integrating with other tools/editors/local environment, I never think of this:) I always focused on how I can make life easier in production :P
Initially I’m trying to target the developers, for now only those who are using Angular :)
So what do you think now? Is that makes sense to pursue? Or maybe those points are not clear enough in landing page! Any further feedback is appreciated :)
Your take on components is interesting.
I know that gitlab integrates with sentry.io in a relatively similar way.
https://sentry.io/integrations/gitlab/
That could be useful inspiration to you.
With that said, this is not clear from looking at the landing page. you might want to find a way to better express this aspect of your solution.
Sentry's gitlab integration is interesting, I also had those idea specially which commit is the culprit, possible hints for the fix and so on but I kept them very bottom of the backlog! yeah I also felt that the landing page need more love and thanks again for your constructive comment 🙂
By the way, there's a little inconsistency in your pricing:
Growing plan: 512MB storage ~100 000 errors
Professional: 2GB storage ~1 000 000 errors
Does the professional plan have a revolutionary compression algorithm? :-)
Yes you're right :) it should be ~400 000 Perfect catch by the way, thanks man, you helped me a lot :)
Hey Omar I've another question, some people suggest me to include a small free tier that might help for marketing and later on they can be the paid customer, what you think?
imho it depends on whether this is really bringing value to you or not.
The idea behind the free tier is to give people the ability to get some value from your product before they pay for it, but there are other potential ways I can think of:
You could also provide several demos, for example a read only dashboard, and that might be enough, depending on your demographic.
No matter which approach you follow, the goal remains the same: provide a teaser to the prospective customer to entice them to pay for it.
Amazing! there are other ways to do stuf instead just a free tier 😀 I think free plan should work for me, I can offer 1 or 2 sprint free so they can understand the product and the value of it 🙂 Thank you Omar :)
if it’s limited in time, make sure to name it Free Trial to avoid misleading people.
Happy to help @treza!
Yes, I'm thinking the plan will be limited in time, so it make sense to have it, out loud! Thanks man, you've been a great help, much appreciated :)
Pretty and to the point, good work
Thank you very much 😀
first thought: better stacktraces for js which finally somebody gets
1st confusion: is the example on the landing how you make it better, no it's like it's now...
2nd confusion: click on demo, then This is demo user, to see live error go to example page and generate some errors!, then dont know what to do
back and 2nd try on landing: ok i got that your stacktrace is just below the crappy stacktrace; but dont find your stacktrace much better
left
Thank you for your feedback 🙂 so the landing page example is not clear enough to convey the message and you found the demo presentation is needed some steps.
Not a developer but I understand what it does. So I would say yes.
Thank you for your kind words 😀