Screenshot API

981 posts

Screenshot API banner
Screenshot API

Screenshot API

@ScreenshotOneHQ

Fast and reliable screenshot API built to handle millions of screenshots a month. Tweets by @DmytroKrasun.

Katılım Şubat 2013
207 Takip Edilen341 Takipçiler
Screenshot API retweetledi
Dmytro Krasun
Dmytro Krasun@DmytroKrasun·
Build your product with a public API in mind, so if needed in the future, AI agents can use it. oRPC supports that (with OpenAPI) out of the box. It provides everything that API routes, Server Functions, and tRPC offer, but even more than that and in a coherent way without any additional dependencies. screenshotone.com/blog/migration…
Dmytro Krasun tweet media
Nic Polotnianko 🇺🇦@nikpolale

@DmytroKrasun glad to see you ended up migrating from server actions! what was the last thing that made you switch? and why not trpc? first time hearing of orpc

English
7
5
43
8.5K
Screenshot API retweetledi
Luis
Luis@iflessthan3·
I used ScreenshotOne for LandingMRR. It was probably the only reason I was able to ship in 36 hours instead of multiple days or weeks. Similarly to the app in the video, the quality of my app directly depends on the quality of the screenshots. Next up is separating screenshots by sections by css selectors to the request. Thanks for the great product!
Luis tweet media
English
1
2
9
1K
Screenshot API retweetledi
Dmytro Krasun
Dmytro Krasun@DmytroKrasun·
Code review matters. People who post the opposite: 1. Are parroting to get attention. 2. Or they don't have experience in engineering or building mostly CRUD. 3. Or they are selling vibe coding platforms. LLMs don't have coherent understanding of your codebase (yet). They generate code that **might** work. It is on you to understand and test their output.
English
49
3
70
3.2K
Screenshot API retweetledi
Dmytro Krasun
Dmytro Krasun@DmytroKrasun·
Currently experiencing a temporary reduction in performance for some ScreenshotOne API requests. The root cause has been identified: our main cluster did not scale due to a shortage of compute resources. Traffic is being rerouted through additional resources and data centers. Performance should already be back to normal.
English
7
3
29
3K
Screenshot API retweetledi
Dmytro Krasun
Dmytro Krasun@DmytroKrasun·
My thesis always was: If I can get one paying customer, I will be able to find 10 more. If I have 10 more, I will find 100. Soon (hopefully), I will get to 1000 paying customers. But! I will not reach 10,000 paying customers in the same niche with the same product. I have some time to figure out what to do next and how to scale. Adding more services? New products? Agents?
Dmytro Krasun@DmytroKrasun

My tiny product (ScreenshotOne.com) is now officially serving 800+ paying customers 🥳 Thanks to everyone who supported me in this journey 🙏

English
37
1
121
12.5K
Screenshot API retweetledi
Dmytro Krasun
Dmytro Krasun@DmytroKrasun·
My tiny product (ScreenshotOne.com) is now officially serving 800+ paying customers 🥳 Thanks to everyone who supported me in this journey 🙏
Dmytro Krasun tweet media
English
108
5
486
33.4K
Screenshot API retweetledi
Andy Hooke
Andy Hooke@andy_hooke·
Last week on Saaspo
GIF
English
12
5
66
2.4K
Screenshot API retweetledi
Dmytro Krasun
Dmytro Krasun@DmytroKrasun·
Talked with @forgebitz about how they use ScreenshotOne in Promptwatch and why they decided to buy instead of build. I don't know how long that equation will last. Maybe, at some point building with AI will be a no-brainer versus buying, but once again our conversation reminded me that to win you need to focus on your customers and your core competitive advantage; everything else can be bought/outsourced. screenshotone.com/blog/promptwat…
Dmytro Krasun tweet media
English
12
1
25
4.6K