Live data from Hacker News

Launch HN: Axiom (YC W21) – No-code browser automation a.k.a. RPA for everyone

news.ycombinator.com

41–50 of 80 posts

Re: Launch HN: Axiom (YC W21) – No-code browser automation a.k.a. RPA for everyone

#42

>using Axiom is 10X faster than writing it in selenium/puppeteer + we handle all the annoying logic you need. We're investigating a node library for this - let us know if it would be useful. As someone who has recently started working with puppeteer, I definitely think a library to alleviate that pain would be immensely valuable.

As a developer about to go down the e2e testing pipeline for our new products and chosen puppeteer, I would also be very interested in this.

for anyone else about to go down the e2e testing road - I recommend checking out cypress.io

Re: Launch HN: Axiom (YC W21) – No-code browser automation a.k.a. RPA for everyone

#43
post #40

I normally hate this kind of animations on websites, but in this case they look really good. (Only on the first page though, when I click on later pages, for instance "Bot Service", waiting for content to show is annoying.)

Thanks, noted! The crane is kind of our mascot at this point, he's been there since the very beginning (even when the product idea was quite different).

Re: Launch HN: Axiom (YC W21) – No-code browser automation a.k.a. RPA for everyone

#45
post #40

I normally hate this kind of animations on websites, but in this case they look really good. (Only on the first page though, when I click on later pages, for instance "Bot Service", waiting for content to show is annoying.)

Awesome glad you like the animations. I have made a note of your feedback; I will strip the page animations out of the nested pages. I still want to add a little something with animation and our branding to give the pages a unique feel, but something small and subtle.

Re: Launch HN: Axiom (YC W21) – No-code browser automation a.k.a. RPA for everyone

#46
post #42

Earlier quoted context omitted.

As a developer about to go down the e2e testing pipeline for our new products and chosen puppeteer, I would also be very interested in this.

for anyone else about to go down the e2e testing road - I recommend checking out cypress.io

Funnily enough, the first axiom prototype we sold customers was on cypress.io - I liked it!

We switched it out for puppeteer as it was more suited as a library for our-case. Cypress is a great batteries-included E2E solution though.

Re: Launch HN: Axiom (YC W21) – No-code browser automation a.k.a. RPA for everyone

#47
post #33
post #31

Earlier quoted context omitted.

Follow-up question, can I screenshot webpages that it visits?

Not currently in the no-code interface! I've seen this requested before. Puppeteer (the library which runs our bots) does support this easily, so we may be able to whip something up if you have a sizeable use-case.

I set up a meeting for tomorrow through your website (look for a meeting with Brendan), we've got a large use case for this and it could really help us out.

Re: Launch HN: Axiom (YC W21) – No-code browser automation a.k.a. RPA for everyone

#49
post #48

Curious about this use-case "booking on a travel website" - are companies using Axiom during a live request to book flight / hotels? What's the need for using Axiom vs using the booking sites API directly?

There are two main ways this can happen:

1) There isn't an API, it's incomplete, or it's otherwise unsuitable. This is more true for smaller vendors, and less true for the bigger ones.

2) The company doesn't have engineering resource to fully implement an API solution, if it does exist. In this case there's somebody doing the manual process, and they are usually the one who actually implements the automation. This is the advantage of being no code! We've seen this a few times - people have been given the job of manually fulfilling requests and they decide they want to try automating it instead.

Re: Launch HN: Axiom (YC W21) – No-code browser automation a.k.a. RPA for everyone

#50
post #48

Curious about this use-case "booking on a travel website" - are companies using Axiom during a live request to book flight / hotels? What's the need for using Axiom vs using the booking sites API directly?

Secondly, I obfuscated the example a little for the startup's privacy.

They weren't booking something, they were cancelling something, and yes there wasn't an API.

Post reply on HN