Really nice, i'd like to use this, and if the license was right probably would if it was OSS.
I think closed source service stuff like this was long over before LLMs came along. Now it's like, I can take a few screenshots and make this myself. At least with open source YOU the developer get to carry on being in the conversation and co-develop, rather than giving ideas to others and being left out
Your order flow has an issue where it's possible for someone to pay for something and not get it. You can either fix this or you might be able to use it to show the value of your product that somebody could see the bug by stepping through your diagram
Great catch and honestly a perfect demonstration of exactly what Flostep is for.
The payment flow on the site is a simplified demo diagram. But you're absolutely right that stepping through a diagram like this is one of the best ways to catch edge cases before they become bugs, that's one of the core use cases we see.
Would love to know: is this something you'd use in PR reviews to catch issues like this early?
It’s hard to imagine someone creating these for PRs? Unless it was auto-generated, but even then it’d only be relevant for fairly large/novel PRs — and then it’s functionally the same as documentation use case.
You’d also probably need some mechanism to visually diff the flowcharts to participate in discussions/changes
Thank you! Presentations are actually one of the strongest use cases, being able to walk an interviewer or stakeholder
through a system one interaction at a time, rather than pointing at a static blob of boxes and arrows.
Would love to know what you'd use it for
specifically — system design interviews,
team demos, something else?
Really nice, i'd like to use this, and if the license was right probably would if it was OSS.
I think closed source service stuff like this was long over before LLMs came along. Now it's like, I can take a few screenshots and make this myself. At least with open source YOU the developer get to carry on being in the conversation and co-develop, rather than giving ideas to others and being left out
Your order flow has an issue where it's possible for someone to pay for something and not get it. You can either fix this or you might be able to use it to show the value of your product that somebody could see the bug by stepping through your diagram
Great catch and honestly a perfect demonstration of exactly what Flostep is for.
The payment flow on the site is a simplified demo diagram. But you're absolutely right that stepping through a diagram like this is one of the best ways to catch edge cases before they become bugs, that's one of the core use cases we see.
Would love to know: is this something you'd use in PR reviews to catch issues like this early?
It’s hard to imagine someone creating these for PRs? Unless it was auto-generated, but even then it’d only be relevant for fairly large/novel PRs — and then it’s functionally the same as documentation use case.
You’d also probably need some mechanism to visually diff the flowcharts to participate in discussions/changes
This looks pretty! Looks to be really good for presentations
Thank you! Presentations are actually one of the strongest use cases, being able to walk an interviewer or stakeholder through a system one interaction at a time, rather than pointing at a static blob of boxes and arrows.
Would love to know what you'd use it for specifically — system design interviews, team demos, something else?