Fixing Navigation, Enhancing GIGI Projects, and Streamlining Stripe — April 23, 2026

Today was a long day, clocking in at around seven hours, but the work done feels significant. My goal for the day was to resolve a few major issues with site navigation, improve the flow of the GIGI project, and streamline the process for integrating with Stripe. What was done? I was able to clear many bugs in the navigation, improve user experience in project management, and resolve many user-reported issues related to the Stripe API.

The first thing I set out to achieve today was to resolve some navigation bugs that had been bothering me over the past few days. One of the issues I was dealing with was that the app was stuck on localhost for some users, and I identified that the issue was caused by an absolute URL that was pointing to the localhost. This meant that users would get stuck on localhost:3001 and be unable to access the live version of the app. After several hours of fixing the problem, I was finally able to implement a solution that would always redirect users from stale localhost origins to the live version of the app. This was quite difficult because previous session storage flags were interfering with the redirection logic, but in the end, I was able to resolve that problem.

To improve the user experience for project owners and admins, I took a look the GIGI projects feature. I wanted to change how delivered artifacts are displayed from a JSON blob to something more user friendly. I created a real handoff UI that had an ‘Open site' button and a notes card with an attached files list. This change will help users understand what to do next and help them navigate their projects. It is nice to see how small changes can improve fluidity in the system.

Another change that I made today is the project-attention badge. Users can see how many projects need their attention without having to open each project individually. The navigation bar will change based on the status of a project, for example if it is ‘proposal ready’ or ‘awaiting payment’. The profile icon will be an active reminder for the user as the dot will pulse. This will be a great way to improve user engagement and lower the chances of tasks being left unfinished.

My focus with recent tasks has been the integration with Stripe. I was able to work around the issues with the new API that caused problems with subscription creation. I noticed the product_data parameter had been deprecated and was throwing errors. Because of this, I had to rewrite some of the code and address the API changes. It also took longer than I anticipated. But, I am glad to say that the integration is going to be a lot more dependable and is going to run a lot more smoothly. I also developed a process for dealing with delinquent billing so that users will receive a clear notifications if their payments fail.

While I was working on these features, I discovered lots of bugs. An example of this was the Google Maps markers flashing on every socket event. This was because there was a cleanup error in the component lifecycle. I had to look through a lot of the useEffect hooks to figure out how to make sure the markers kept their state without being re-rendered more than needed. These types of problems are usually the most time-consuming, and I don’t like to admit that they are part of the learning process more often than not.

From the work I did today, I can clearly see all the progress that I have been able to make, and it really shows how much work has been put into building the platform. There are a lot of challenges, but it is really good to see everything fit together so well. With every feature I am able to add and each error that I fix, I get closer to the vision of my $1 billion company seamless business. I have set the bar pretty high, but little successes are all contributing towards achieving it.

Reiterating what has been done today, navigation and project management systems were improved, and user experience enhancements were made. All the fixes and improvements are features of making the hashtag.org and agentic web more robust and scalable. I'll continue to work on these features ongoing, tackling new challenges as they come up. I'm in it for the long haul!