
The next project I am building is ScreenshotOne — a simple screenshot API for websites.
Screenshot API — sounds boring, yes? But my goal was to build any project and try to get the first paying customers. I had not planned to do an exciting project.
I want to test the saying that "idea does not matter, but the execution is what matters". I picked up the idea mainly randomly but at the intersection of my current back-end development skillset and additional challenges like UI, UX, CSS, SEO, and marketing.
By building an actual project, I need to fill the gaps in my skills, and I have a lot of gaps.
I am not sure that I agree that you should choose the domain you love and are excited to work in. Passion is not something you can control by definition. And it can fade with years, months, or even weeks.
But if you have success with something, you will love it and tell everybody that this is your true passion or even a calling.
The more I build such a simple thing, the more I find many opportunities to do new businesses.
I write deeply technical articles to promote the project. For example, I wrote about how to take a screenshot with Puppeteer. I would outsource this copywriting, but I have not found an agency that could do it as well as I demand.
I have not found a decent SaaS template for Go, or those that I found were outdated. So, I reinvent the bicycle by myself. It is an excellent opportunity for the business itself.
I can continue how many new ideas I found by building just this simple small thing.
The project is in the middle phase, I am not polishing it yet, but I am gradually creating different parts of it — docs, payments, dashboard, etc.
If you are interested in how far I can go, you can follow me on Twitter.
Start whatever, whatever, but start.
Not gonna advocate for following your passion, however working on what you love probably has some upsides like making content creation a breeze.
I've read those blog posts before and I wonder did you consider sharing those on sites like dev_to, hackernoon etc. Seems like a good fit. Also waiting for the post about paddle implementation if it works out or not.
Thanks for the feedback.
I am not against following one's passion. I wanted to admit it might not work in the long term. You might have a new interest. Passion is, by definition — a "strong and barely controllable emotion."
I like the idea of posting to the sites you mentioned. I need to try.
Thank you for your feedback, as always, you are 🔥!
Agreed and following a passion doesn't guarantee success, only easen the process.
I don't recall which is which but some of them offers seo friendly back links, jfyi.
You are the one on fire, keep on building.
How do you plan to differentiate this from the other screenshot APIs out there?
A lot of options:
But I am still at the basic functionality. What would you recommend? Do you see any exciting additions to differentiate?
I'm afraid I may not be the best person to comment on this as I don't really have a use-case for headless screenshotting at the moment
Let me know if / when you would like testers to try it out (c#). I am working on a website crawler and was planning to add screen shots of potentially broken pages as a future feature.
Also happy to proof read to pay it forward.
Thank you so much. I will update you when ready.
Some times the most boring projects are the best ones because there is no competition :p. Come an build your product in the WBE Space