Day 163: Browserflow API Considerations

product

When I think about what’s required to launch Browserflow (I’m quite far from doing that, but it’s useful to consider early), three major considerations come to mind:

  • Power
  • Reliability
  • Stability

Power

  • What kinds of flows are possible?

Reliability

  • What kinds of websites do flows work on?

    • Or since Browserflow is intended to work on every website, the better question might be: What kinds of websites do flows not work on? Why not?

  • Do flows run consistently and produce the same output given identical inputs?

Usability

  • How easy is it to build flows?
  • How easy is it to debug flows?
  • How easy is it to run flows?

I’m focusing on the power aspect this week — the goal of Browserflow is to be able to automate anything a human being can do in the browser, and it’s not quite there yet.