The idea: why I started developing Planny

Why Planny? Why did I start developing it?

It started over 2 months ago when I was searching for a simple content scheduler for my team. I had found many, but none had these  features at the same time:

• minimal ui
• calendar view
• simple draft management
• simple account management
• only the necessary analytics

So, in my spare time, I started developing a  scheduler that could meet my needs.

I had great challenges to overcome; I was a one-man band. I worked on the backend, frontend, UI/UX and also the infrastructure.

The stack I used to do everything:

• Programming languages: NextJS, NodeJS, MySQL
• Hosting: Vercel, AWS, PlanetScale
• Other: Stripe, Plausible, Figma

It took me 2 months but I’m happy and I learned new stuff along the way.

In the last few days, I finished developing what it was missing and now I’m in love with the result:

A quick and easy-to-use Twitter calendar planner with a heavy focus on the content, simple draft management and useful and easy-to-read analytics for accelerated growth.

What are the differences between Planny and content schedulers?

• Finally a clean, distraction-free calendar and schedule, I don't want a thousand buttons to do one thing;
• The essential analytics to grow;
• Super easy multi-account management.

Since being an indie hacker for some time (and rarely finishing a project ;)) I am glad to finally show you the beta release of Planny.