New season, new project: I need you πŸ‘‰ πŸ™

Pierre - May 17 '19 - - Dev Community

A quick update

I haven't written a lot lately, I was very busy with my first own, and co-founded, company: PricingBot a price monitoring service for e-commerce.

Things well went, we brought in some cash, and currently, the whole thing works well on autopilot.

But lately, my partner and I decided to build something new, something for developers.

One API to rule them all

During our short career, we did a lot of scraping, and we all had the same problems:

  • proxy handling
  • managing a large fleet of chrome headless
  • captcha
  • JS rendering
  • other

We know all of this can takes a lot of times. We wanted to make a tool that allows people to easily scrape web pages, on the go, without having to take care of all this.

This is why we've decided to build ScrapingNinja πŸ•Ά πŸ•· πŸ•Έ, the easiest scrapping API on the web.

I'd love to have your input on the idea, so if you could answer those 3 questions on the comment I'd be forever grateful.

Getting feedback when you have an idea can be tough and we really care about the comments we receive from the community.

Here is what I'd like to know:

  1. What are you most pain point when you scrape (proxy / js rendering / latency / capcha / ...)
  2. Would you use such an API?
  3. How many people do you know that could use it?

If you answer those, thank you very very very much πŸ™.

Continuing my blog

If you liked my last post about the best time to post on dev.to last month,
I plan to post one about tags analysis early next week.

I'll also try to share as much as possible about this new project with the community if there is interest in it.

Thank you for reading

Usually, I blog about more tech stuff:

PS: We built the landing page with Landen and I must say it is awesome for someone like me who is very bad with design/font/color. I can't recommend it enough for people who need to quickly put their ideas in front of someone else's eyes.

. . . . . . . . . . . . . . . . . . . . . . . . . . .