Eager

I wrote a version 1 about 2 months ago. It was "okay", but it was clunky and the design wasn't as clean. I rewrote all the code (took me 10 days). There are still some minor bugs, but it's much better. Because the documentation sites themselves are part of the product, I felt that if it sucked for me, it would suck for customers.

I was using the old one myself, and felt **so much friction**. If I hated using it, I can only imagine what customers would feel. So, I redesigned it.

Adding some sort of rollback ability to the app.

Trying to match the key bindings of Gmail with that of the messages view in the Eager app.

I've been dogfooding my own work for the last 4 months, and really hated it when I accidentally close my browser's tab in the middle of typing a message. Enter... AUTOSAVE. Now I can go back to where I left off... 😊

Took about 2 days, but very happy with the result: [1] Handles per seat pricing [2] Uses Stripe's prorate feature to credit unused time [3] Syncs with Stripe for plan features (via metadata).

Working on an email that renders externally received emails is challenging. There are so many quirks in how emails are formatted. Definitely this is the "secret sauce" in building apps like these.

If you're working on something that needs to render emails (that you receive), feel free to ping me and I'd be happy to share what I know.

I had already added this to the user preference section, but I figure onboarding might be a good time to let the users choose as well.

Search / filtering is one of those useful (but really, really boring) parts of the app to add. Here, I added a filtering ability for posts that users create. It uses JavaScript to detect keyup events and sends searches to the server.