Get live statistics and analysis of Marc 🇨🇦🇹🇹🇫🇷🇧🇧's profile on X / Twitter

🧘‍♀️Staying Focused & Avoiding Scope Creep Interesting day today. I worked on @RememberNameApp and added support for multiple images per contact, which was a request from users. I also improved the import/export experience, though there’s still a bit more to do - especially with importing CSV files that have been edited. That part isn’t as solid yet. I’m reminding myself to stick to a weekly update rhythm, even if there are still bugs or feature requests in the backlog. It’s so tempting to keep fixing just one more thing…then another…and before I know it, what should’ve been a quick update spirals into days (or even weeks!) of scope creep. 🧟‍♂️ It’s perhaps better to generally ship small, focused updates than to endlessly polish and delay. Obviously bigger updates may take more than a week. Speaking of updates - pushed the update to Apple today. 🎉 Main highlights: •Added support for multiple images •Fixed the recent contacts widget, which broke after a major refactor Good momentum today. 💡The key lesson: Stay focused, avoid the dopamine trap of endless fixes and ship on schedule.

I finally fixed the widget for @RememberNameApp - the one that shows the most recently added contacts. 🎉 Turns out the issue came down to two separate containers: one for CloudKit and one local. They weren’t communicating. So even if you added a contact in Remember Names, it would go to the CloudKit container, but the widget wasn’t accessing the same container - leaving it empty. 🤦‍♂️ The real fix was to use a unified container. Simple in theory, but there was a hidden trap: the file defining the unified container wasn’t being added to the Xcode project… Why? Because when I first started Remember Names a year ago, I had set up Xcode to require files to be manually added to the project - likely to give myself more control. 🔐 But with AI tools now generating files automatically, this setup worked against me. The AI generated the file, but since it wasn’t added to the project automatically, it wasn’t getting built. I thought I had changed all the folders to accept files automatically but turns out I didn’t. So despite multiple attempts to fix it the widget never had what it needed and I wasn’t realizing why! 😫 What finally solved it? Slowing down and investigating what was really happening under the hood - not just blindly following suggestions or outputs. The AI couldn’t catch the problem, but because I took the time to understand how Xcode, file management and the containers were all working together, as well as which files were needed, I was able to spot the disconnect.😮‍💨 This reminded me how crucial it is to understand your tools, not just use them. If I hadn’t stayed curious…if I hadn’t stopped to trace the dots…I might still be stuck. Now that it’s fixed, I can move on to other things I’ve been putting off. Going to do some final testing today and hopefully push an update by tonight or tomorrow. 🤞

🚀 Morning Momentum & Marketing Started the day strong. Did some light marketing - responded to people on X who engaged with my recent posts and tried to offer some value in the communities by replying to posts I resonated with. Scrolled Reddit briefly, but didn’t find much related to remembering names today. Thought I might’ve checked TikTok too, but can’t recall clearly…kind of a blur there. What did come into focus though was the realization that I needed to reconnect with my customer segments and channel strategy for Remember Names. That got me thinking about an old favorite tool of mine - the Business Model Canvas. 👻 Reviving an Old Concept I used to love using the business model canvas. It gave me a clean snapshot of a business’ entire structure - market segments, channels, revenue streams, everything. But recently, I realized: 📌 There’s no modern, well-designed BMC app on the App Store 📌 Everything I tried felt too basic or outdated 📌 Notes + task managers = chaos when it comes to storing business model iterations So I decided: I’m going to build my own Business Model Canvas app, specifically designed for indie developers like me - especially those of us with ADHD. I need a dedicated space to park my ideas and plans without the clutter. 👨‍💻Developing the BMC App I began developing the MVP with some basic functionality: •Fill out each BMC section (customer segments, channels, etc.) •View the full canvas in a clean, visual format I continued to expand the vision. 💡 Added content strategy planning directly into the app. Now I can: •Map which channels serve which customer segments (e.g., TikTok for students, LinkedIn for networkers, Reddit/X for devs and ADHDers) •Add content types (journal tweets, bug fix videos, tutorials) and assign them to platforms •Track publishing frequency (e.g., 3 journal tweets per week) and monitor execution progress This way, if I skip a few days, I can come back and instantly reorient myself. No more wondering, “Where did I leave off?” ❓Why I’m Building This As someone with ADHD, I need structured tools that reduce overwhelm and allow me to iterate quickly. ❌ Spreadsheets? Clunky on mobile. ❌ Notes apps? Too messy. ❌ Task managers? Not purpose-built. ✅ My custom app? •Always accessible •Easy to update •Purpose-built for messy idea flows •Tailored for product-building & marketing focus App Progress After a few hiccups, got the build working again. 🚧 UI still needs polish 🧪 Testing flows next 📹 Might record a walkthrough or demo and get feedback from other devs This app could be perfect for indie devs, founders, or anyone trying to keep their vision straight while building something. Thinking about entering it into @RevenueCat #Shipaton. Worth exploring. ✍️ Final Thoughts Today reminded me how much clarity I gain from building tools that reflect how I think. If I get this right, it could help others like me - and make the process of building, documenting, and marketing smoother and more aligned with reality. Now that the structure is in place, I can test, iterate, and hopefully eventually monetize it. For now, I’m excited by the momentum. Not perfect…but progress.

💫Turning a 1-Star into a story Just wrapped up today’s session. I finally posted a new video on X - a response and fix to a 1-star review on @RememberNameApp. The review definitely stung at first, but instead of letting it throw me off I decided to turn it into a story worth sharing. The issue was valid…the location-based notification wasn’t triggering so I fixed it, tested it, and documented the process. I shared the whole journey under the #buildinpublic tag. It felt good to be transparent about the challenge, the fix, and the thought process. It’s a step forward. Key updates: •Location-based notifications are working: go somewhere, and if a name is tagged to that place, you’ll get a reminder. •Major refactor done - modernized ALL the code so the UI feels clean and responsive. •Added a congratulatory screen post-subscription…small touch but it feels right. The foundation is finally strong. So the focus now shifts to marketing and storytelling - daily posts, demo videos, and audience-specific messages. Let’s see how far this can go.

⭐️ 1-Star Reviews, Real Feedback, and Real-World Testing A few days ago I started the day by checking the App Store, only to see a 1-star review from a user named Charles_24 with the headline: “Don’t buy this app.” His reasoning? He claimed the app says it’s location-based but isn’t, making it “more or less useless.” That stung. I worked hard to build @RememberNameApp and it’s frustrating to get a public review like that - especially without any direct feedback or chance to respond. My first instinct was to be defensive, but I took a breath and stepped back. What was he actually saying? I reviewed the location features: •Sorting names by proximity? ✅ Working as expected. •Location-based reminders? ❌ Not working. So yeah, he was partially right. The feature wasn’t triggering. Still, I wish he had reached out first. But this is the reality of building for users: you’ll always have some users who don’t communicate, just criticize. Rather than stay annoyed, I decided to turn this into a learning opportunity - not just for me, but for others. I’d record the process and share it as a buildinpublic story. Documenting the real ups and downs. But…everything that could go wrong did go wrong. •Forgot to charge my phone and watch last night. Both were almost dead. •Started recording - got halfway through a scene and wanted to redo it with a better transition. Just as I started re-recording the neighbor fires up the lawn mower. •Tried testing the notification by biking to a nearby playground (set as the location trigger in the app), but realized I couldn’t film my watch while riding. •Had to walk instead. Bright sun = glare on the watch screen. •Phone battery hit 3%, then 1% while recording. •Got interrupted mid-test by messages from wifey. •And finally…the notification didn’t even trigger. 😫 By the time I got home, I was sweaty, low-battery, and missing half the footage I wanted for the story. I didn’t get to shoot the wrap-up scene in the park, where I planned to talk about lessons learned. Buildinpublic? More like failinpublic… All of this reminded me just how hard documenting while building actually is. It takes time, skill, and a lot of patience. It’s effort that could easily be spent just fixing bugs or improving the product instead. But I still think it’s worth it. Not many developers are consistently recording video updates - and I’ve seen interest grow since I did my 30-day buildinpublic video streak. It’s becoming a thing. Still, it didn’t go as planned. But I was determined to fix the bug, retry the test, and record the second half later on. Not perfect…but progress. That’s the journey.

🧠 Memory Tips (Finally) Earlier today @SamGherman replied to a post and said he downloaded Remember Names. He liked it but…he thought the app would offer mnemonic-style tips for remembering names - not just recording them. That was part of the original plan... 🫠 Somewhere between polishing features and prioritizing fixes…I just forgot about it. So his comment was a great nudge. ⸻ 🤖 Alex to the Rescue I jumped into action using @alexcodes_ai to implement a basic version of the feature. 🧠 Added a new “Memory Techniques” tab 🗺️ Swapped the Maps tab out of the main bar ➡️ Moved Maps into the relevant Groups and People tabs 🔁 Updated widgets, intents, and internal routing It wasn’t just a cosmetic change…the restructure touched key parts of the app’s logic. Without Alex’s help this would’ve taken MUCH longer to implement. ⸻ 🧪 Still Needs Polish Right now, the UI is very minimal…maybe too plain. But it’s a solid start. The hard stuff’s in place. I’ll keep testing and refining over time. That’s what this is all about: ✅ Listening ✅ Iterating ✅ Building better, bit by bit ⸻ 🙏 Thanks Sam! App dev can feel like guessing in a vacuum sometimes but small moments of feedback like this help guide direction and improve the whole product. Hope you see the update when it’s fully rolled out…and like it!🤞

⭐️ 1-Star Reviews, Real Feedback, and Real-World Testing A few days ago I started the day by checking the App Store, only to see a 1-star review from a user named Charles_24 with the headline: “Don’t buy this app.” His reasoning? He claimed the app says it’s location-based but isn’t, making it “more or less useless.” That stung. I worked hard to build @RememberNameApp and it’s frustrating to get a public review like that - especially without any direct feedback or chance to respond. My first instinct was to be defensive, but I took a breath and stepped back. What was he actually saying? I reviewed the location features: •Sorting names by proximity? ✅ Working as expected. •Location-based reminders? ❌ Not working. So yeah, he was partially right. The feature wasn’t triggering. Still, I wish he had reached out first. But this is the reality of building for users: you’ll always have some users who don’t communicate, just criticize. Rather than stay annoyed, I decided to turn this into a learning opportunity - not just for me, but for others. I’d record the process and share it as a buildinpublic story. Documenting the real ups and downs. But…everything that could go wrong did go wrong. •Forgot to charge my phone and watch last night. Both were almost dead. •Started recording - got halfway through a scene and wanted to redo it with a better transition. Just as I started re-recording the neighbor fires up the lawn mower. •Tried testing the notification by biking to a nearby playground (set as the location trigger in the app), but realized I couldn’t film my watch while riding. •Had to walk instead. Bright sun = glare on the watch screen. •Phone battery hit 3%, then 1% while recording. •Got interrupted mid-test by messages from wifey. •And finally…the notification didn’t even trigger. 😫 By the time I got home, I was sweaty, low-battery, and missing half the footage I wanted for the story. I didn’t get to shoot the wrap-up scene in the park, where I planned to talk about lessons learned. Buildinpublic? More like failinpublic… All of this reminded me just how hard documenting while building actually is. It takes time, skill, and a lot of patience. It’s effort that could easily be spent just fixing bugs or improving the product instead. But I still think it’s worth it. Not many developers are consistently recording video updates - and I’ve seen interest grow since I did my 30-day buildinpublic video streak. It’s becoming a thing. Still, it didn’t go as planned. But I was determined to fix the bug, retry the test, and record the second half later on. Not perfect…but progress. That’s the journey.

🧠 Memory Tips (Finally) Earlier today @SamGherman replied to a post and said he downloaded Remember Names. He liked it but…he thought the app would offer mnemonic-style tips for remembering names - not just recording them. That was part of the original plan... 🫠 Somewhere between polishing features and prioritizing fixes…I just forgot about it. So his comment was a great nudge. ⸻ 🤖 Alex to the Rescue I jumped into action using @alexcodes_ai to implement a basic version of the feature. 🧠 Added a new “Memory Techniques” tab 🗺️ Swapped the Maps tab out of the main bar ➡️ Moved Maps into the relevant Groups and People tabs 🔁 Updated widgets, intents, and internal routing It wasn’t just a cosmetic change…the restructure touched key parts of the app’s logic. Without Alex’s help this would’ve taken MUCH longer to implement. ⸻ 🧪 Still Needs Polish Right now, the UI is very minimal…maybe too plain. But it’s a solid start. The hard stuff’s in place. I’ll keep testing and refining over time. That’s what this is all about: ✅ Listening ✅ Iterating ✅ Building better, bit by bit ⸻ 🙏 Thanks Sam! App dev can feel like guessing in a vacuum sometimes but small moments of feedback like this help guide direction and improve the whole product. Hope you see the update when it’s fully rolled out…and like it!🤞

💫Turning a 1-Star into a story Just wrapped up today’s session. I finally posted a new video on X - a response and fix to a 1-star review on @RememberNameApp. The review definitely stung at first, but instead of letting it throw me off I decided to turn it into a story worth sharing. The issue was valid…the location-based notification wasn’t triggering so I fixed it, tested it, and documented the process. I shared the whole journey under the #buildinpublic tag. It felt good to be transparent about the challenge, the fix, and the thought process. It’s a step forward. Key updates: •Location-based notifications are working: go somewhere, and if a name is tagged to that place, you’ll get a reminder. •Major refactor done - modernized ALL the code so the UI feels clean and responsive. •Added a congratulatory screen post-subscription…small touch but it feels right. The foundation is finally strong. So the focus now shifts to marketing and storytelling - daily posts, demo videos, and audience-specific messages. Let’s see how far this can go.

👋 Hey @RevenueCat and @stevepyoung! @RememberNameApp is a relaunch of a 10yr old idea to build relationships for myself and others. Learnt perfectionism kills progress and I’m a new indie dev willing to try new things. Let’s #buildconfidence together! 🌍😎🎉 #RCGrowthChallenge