My attention span had been shot to pieces lately. Reading, meditation and not mindlessly browsing have been great in restoring it. So, a tiny update (amongst others):

New credit icon added 😍 #buildinpublic

I thought I was generally good at receiving constructive criticism..

Watching a 20min video of someone critiquing my work wasn’t easy watching 😅. It’s probably something I’ll have to get better at and overcome, but now: I have new tasks to work on ✅ #buildinpublic

youtube.com/watch?v=xFFs9U… current watching #buildinpublic #inspiration

The smallest of tweaks. Using @stayinsession while I create and work through some UX changes based on feedback #buildinpublic

Back from a break with a better work/life balance.. Currently a month behind my original timeline 🙃

Testing feedback has been positive. I need to overcome some apprehension about pushing it out there to people #buildinpublic

I've been working on a big feature and a lot of React refactoring.

I'm avoiding over-optimising and just focusing on what the user sees. This helps me keep moving quite fast, but I do run into some 'this is ridiculous, I need to refactor' scenarios 😅

#buildinpublic

Visual Code Studio asks me to select a default formatter EVERY time I run the 'Format Document' command 🙃. I select one, rinse and repeat.

Ok I just solved it. I also had to specify the formatter in Settings. #vscode #visualstudiocode #buildinpublic

#buildinpublic update, probably a week behind my planned go-live schedule.

API server issues slowed me down, but also obvious improvements I had spotted, and didn't want to release to testers without.

🎯I need to update my changelog tomorrow (it's not automated :)

I forgot to include #buildinpublic above, tweet wasted 🙃

This evening I've been investigating why my Node.js API process is (what appears to be) randomly dying.

Logging stdout / stderr doesn't seem to show why. The JS errors logged don't seem to be the cause either 🙃

On the more productive side I've added security #buildinpublic

Is anyone not using email verification? I see the need, but I think it does add a barrier to the experience 🤔

#buildinpublic #indiehackers

My potentially overly ambitious feature is now in testing - Auth system with credits to access data 🔒

Also, I think my search button needs to be indigo, or it all needs to be blue 🤔🙃

🎯 New launch date = this weekend

#buildinpublic #indiedev

I've arrested the decline in my indexed pages! 🤩 I was going to have 0 indexed pages by the end of the year at the previous rate. Let's see how this progresses..

#buildinpublic #seo #searchconsole #indiedev

Pink or blue?

I need to add my search bar here instead of the newsletter signup as I'm annoying myself by having to scroll down on the landing page to search. #buildinpublic #AskTwitter

I move more redundant code and clean up / improve a few more things. It's not lightning quick but it builds within a few minutes and that's good enough (TM) for now.

My lesson: problems require thought and enquiry - break things down 🏗️ #buildinpublic

New layout for data pages on @PropertyWisdom1. A few changes have been made to improve load-speed - this is still an issue with my pages..

Auth work has held me up, but my goals remain unchanged. First paying customer by the end of June #buildinpublic

Google Search Console report 😓

I'm not really pushing SEO right now but I have work to do. Too many pages looking too similar I think #seo #buildinpublic

So, I've been creating my own auth service with node / jwt. This sounds a suboptimal use of my time, but I have not been happy with the performance / implementation (Auth0 still requires a lot of setup if using custom data).
#buildinpublic

I realised the pricing / signup flow still wasn't defined - I had an idea but it was hazy.😓

I had been wanting to just code parts, but this evening I wrote down the user journey. It takes deep thinking and that's probably why I had put it off #buildinpublic

Reminder to self: Launch @PropertyWisdom1 to the public by the end of June.

#buildinpublic