Building Panda's Notebook

Why I got tired of tab-switching and built a unified workspace for songwriters.

Hey everyone,

I’m Jason, creator and developer behind Panda’s Notebook.

If you write lyrics, produce tracks, or work with vocal arrangements, you probably know the exact friction that led me to start this project.

For a long time, my own writing workflow was a messy web of open windows:

• A text editor open on one side of the screen

• A browser tab running a legacy dictionary or phonetics site

• A separate audio player looping a draft beat

• An AI window open to test line variations or meter ideas

Every time you jump between four different tools to check a slant rhyme, adjust a line length, or restart an audio loop, you break your flow state. Creative momentum disappears in the context-switching.

That friction is why I decided to build Panda’s Notebook from the ground up—an all-in-one, distraction-free desktop and web workspace designed specifically for the real-world flow of lyricists and music creators.

What sets it apart:

• Inline Computational Phonetics: Real-time CMU-Dictionary phonemes, syllabic stress analysis, and line-terminal slant rhyme extraction directly inside your primary editor.

• Integrated Beat & Audio Sync: Loop instrumental drafts directly alongside your text without juggling media players.

• Context-Aware AI Assist: Inline AI assistance that respects meter, genre cadence, and structure—acting as a co-pilot rather than trying to generate generic text for you.

• Unified Cross-Platform Build: Native desktop and web builds keeping everything lightweight and immediate.

• Packed with tools: 40 + Features Launch in the apps first release and it's only the beginning.

We are gearing up for our official release soon, but I wanted to open up the floor early to hear from other creators, developers, and writers in the community.

I'd love to hear your thoughts:

1. What is the biggest bottleneck in your current songwriting or creative writing workflow?

2. What single feature or tool do you feel legacy editors consistently get wrong?

Drop your thoughts below—I'll be hanging out in the thread to answer questions, share dev updates, and take notes on what you want to see built next!