Tweet
Was testing different newsletters on LettrInbox, found out the API I use to grab favicons from a newsletter's domain sometimes just doesn't work, although it used to. The error message doesn't help, need to start working on an alternative I guess...

#buildinpublic
Day 32 of #buildinpublic

Added a cron job to fetch new newsletter issues to improve the speed of the app as the requests could take some time (up to 15 seconds), which is bad for the user.

Gonna improve my landing page copy before launching, a lot of mistakes here and thereπŸ˜…
Day 31 of #buildinpublic

In my first month of building in public, I released an MVP with tons of bugs and I'm now settings up the v1 of LettrInbox for production.

Thanks to the Twitter community and @BetaList, I got ~40 people on my waitlist.

Launch is coming πŸŽ‰
Day 30 of #buildinpublic

Everything is working, finishing up the responsive version as +50% of my website visits are from mobile, which should be done by tonight.

Also adding a way to track user events, will probably be usefulπŸ˜…
Day 29 of #buildinpublic

I stumbled across some weird bugs during my tests. Luckily not too many, hopefully I'll get them fixed by tonightπŸ˜…

That's my last step before launching. Fix everything, then launchπŸŽ‰
Day 28 of #buildinpublic

Had a long day away from the PC, didn't get the time to do any work. I'll catch up the tomorrow and try to finally launch LettrInbox πŸ˜…
Day 27 of #buildinpublic

Just finished up with all the features, gonna take some time to test everything properly and then it'll be time to push to production πŸŽ‰
I was locking some features for the free plan of LettrInbox, which was my last task, but noticed that I have no way to calculate how many issues a user receive per month as I still haven't implemented dates.

That's what I get for trying to avoid handling datesπŸ˜‚

#buildinpublic
Day 26 of #buildinpublic

Finished with the Stripe integration, just need to add a small "thank you" message πŸŽ‰

All that's left is to limit the features depending on the user's plan, which shouldn't take too long.

After that it's done πŸŽ‰
Day 25 of #buildinpublic

Finally fixed all bugs I found and I'm almost done with the Stripe, just need a cancel option.

Added a simple layout for users to upgrade & downgrade their subscriptions from their settings.

It's coming together, hopefully I can release it tomorrow πŸŽ‰
I needed to write a 5 line serializer, and for some reason I got really lazy.

I decided to try Github Copilot to write it, then proceeded to play with it for the next hour.

Although not perfect, it's incredible how much time it can save you.

#buildinpublic
Day 24 of #buildinpublic

Worked on some bugs and found a free API to grab favicons from a domain to replace the buggy package I was using. Tonight I'll integrate Stripe... I hate implementing subscriptions 😭
Day 23 of #buildinpublic

Didn't get the time to work at all yesteday, but I'm keeping my goal of lauching monday. That gives me the entire week-end to do the following:
- Stripe implementation
- Landing page improvement
- User on-boarding
- Prepare a launch email for my waitlist
@meekscreative Good luck with your journey! I started with 0 followers 20 days ago and had decent traction to my product. Just be consistent with your update and the #buildinpublic community will be there for you πŸ™‚
Day 22 of #buildinpublic

Didn't get the time to work on LettrInbox today. Managed to get 2 hours to spare before going to sleep, hopefully I'll manage to get some work done πŸ˜₯
Day 21 of #buildinpublic

Working on the subscription system. Currently building a simple UI for the users to order and modify their subscriptions.
Just finished all my features, and they work, as far as I know πŸ˜‚

Got ideas popping everywhere in my head, but I need to control myself and focus on what's needed to launch:
- Subscriptions
- Responsive design

I'm gonna try to do those tonight πŸ˜…

#buildinpublic
Day 20 of #buildinpublic

Got straight into building today and I managed to get almost everything done, just some minor fix that need to be done before deploying πŸŽ‰

I should be able to finish by tonight, and maybe if I have the time also work on my copy.
Day 19 of #buildinpublic

Before getting into building, I took the time to send out some emails to my waitlist. I want to go back to building but I really need to improve my landing page copy πŸ˜…
Yesterday around 20 people joined my waitlist and I'd like to thank them.

I was wondering if I should send a good looking HTML email or go with the plain text approach, which I feel is more personal.

What are your thoughts? πŸ€”

#buildinpublic #indiehacker #indiedev