The itch I had to scratch Every time I wrote a technical blog post or generated docs, I...
The itch I had to scratch
Every time I wrote a technical blog post or generated docs, I needed code screenshots. I'd open Carbon, paste my snippet, tweak the theme, hit export, download the file. Repeat for every snippet. It was manual, slow, and couldn't be automated.
Carbon is beautiful. Ray.so is slick. But neither has a REST API. If you want code screenshots in a pipeline — you're on your own.
So I built SnapMyCode.
What it is
I have this habit of sharing code snippets online. Not tutorials. Not threads. — "Look at this...
If you share code on social media, you've probably used Carbon, ray.so, or Snappify at some point....
We post a lot of code to X and LinkedIn, and screenshotting it by hand never stayed consistent. This is the workflow we use now:…
Hey everyone, I'm a software engineer and this is my first SaaS. I kept seeing the same problem:...
I'm Rishab. Every time I shipped an iOS app, I'd lose 2 days fighting Figma trying to make App...
We’ve built a local-first App Store screenshot native Mac tool where the project file is a...
