WHAT I'M WORKING ON
Eating my own RocketSim-Food
This week I realized something interesting: I'm no longer an end-user of RocketSim myself as much as I used to be.
I knew this, of course, but I didn't realize it enough. Back in the days, I worked on iOS apps on a daily basis at WeTransfer. I was in a constant need of what RocketSim offers. These days, I'm developing new RocketSim features based on creative insights.
When I started the From App Idea to 10K MRR YouTube Series, I also started working on an iOS app. I became my own end-user again! The impact of it is just unmatched. Features I thought worked great, don't work how I imagined it at all. They're not bad, I'm just able to apply my user-experience study background more precisely.
It results in a parallel development experience. While developing the app for the YouTube series, I'm also actively improving RocketSim. Small UX improvements, but also large stability improvements for something like the Network monitoring feature.
At the same time, I'm embracing AI. In fact, AI is writing much more code than I do these days. Anything I can do to make AI more knowledgable on the outcome of the code it writes can improve the development cycle. This is where the future of RocketSim comes into place: I want it to give AI agents eyes.
One of the first things I've been running into are network request optimizations. I noticed duplicate requests in RocketSim's Network Monitoring, but what if AI could notice these? What if I could hook up an MCP server and let AI tell me what to improve? What if AI could tell me what opportunities there are inside the network responses?
Becoming my own end user has changed my perspective again. I'm back to ideation creativity, and I'm embracing it.
This is also the final SwiftLee Weekly of 2025. With that, I want to thank you for all your support, for continuously reading my newsletter, and I want to wish you all the best for 2026!
Antoine