I'm starting work on a new project. Before I start, it's important to think about why you're building and the outcome you're hoping for.
Understanding this can help inform the decisions you have to make while building.
Before I started working on Bluesky Directory I had a clear goal in mind: Learn more and how AT Protocol & Bluesky worked, and engage with the community.
I decided that a directory was a good way to do this. Simple to build, which allowed me more time to learn about the underlying platform. While a directory is primarily for people seeking content, it is also for people providing content, in this case developers in the Bluesky ecosystem.
Further more, building in public allowed me to share what I was learning and engage with those developers on Bluesky.
As I start work on a new project, I'm thinking about my goals now.
I'd like to continue working on Bluesky Directory, but I don't see a clear path to profitability (the biggest expense being my time.)
I could plaster the site with ads and generate some revenue, but I think stopping "enshittification" should extend past the Bluesky clients.
I don't want the directory to be pay to play, and give all great products the exposure they deserve, not just those with means to pay for it.
The clear path to freeing up more time from client (freelancing) is to build a product that Bluesky users would be willing to pay to use.
This would give me more time to work on both the directory and more generally in the Bluesky ecosystem.
It may be too early for users to pay for products related to Bluesky, but with the platform growing quickly, waiting may mean missing the opportunity when it arrives.
I'm going to spend a little time researching the best thing to build, I already have a few ideas, but nothing is decided.
The ultimate goal is to build a product that users are willing to pay to use. This will allow me to reduce my client work, and spend more time building in the Bluesky ecosystem.