Hi! Welcome to the AI Architects Community. Take a moment to map out your goals and introduce yourself to the group. (✄ copy/paste template below) What are you building? What's your 3 to 6 month goal? What's your biggest blocker? What are you most excited about?

Stephen, The Popebot repo says Slack is coming soon, I am going to start building a slack comms channel and a Teams comms channel. As you know I am building a Popebot version for CPAs and accounting pros and they want to work in their “comfortable” space, so adding slack and teams is important for my goals. I have some questions. I will fork off the main, your, repo and build the slack channel but how do you suggest I handle other things outside of ThePopeBot if I add them? My goal is to mainly keep the popebot function as it is but this week I created a survey server that uses the popebot chat but in an external next.js webpage and runs a discovery conversation. Just 11 interactions in and it is amazing… How would you suggest adding functions like that, that are for the bot I am going to sell? When I ask how I mean GitHub wise. I think I understand your repo is forked and I can sync updates to my repo and then I just build in my project folder? Your thoughts and wisdom are appreciated.

A lot of people are confused about Claude’s interfaces. Not because they’re bad at AI.Because the differences are honestly hard to understand at first. Chat. Cowork. Code. They look similar…but they’re built for different types of work. So I made this simple breakdown for my own understanding and turned it into an infographic. Here’s the simple breakdown: 1. Chat = everyday AI assistant This is what most people need most of the time. You can: • ask questions • connect tools like Notion, Slack, Gmail • save memory • reuse prompts and workflows • share files and dashboards Example:A marketing manager can plan campaigns, summarize meetings, write emails, and organize docs without touching code. But there are limits: • it can’t properly update project files • context gets messy over time • no real automation • you still have to manually run everything 2. Cowork = AI teammate This feels like Chat…but with way more power. You can: • edit files directly • run scheduled tasks • connect live dashboards • use plugins/tools • automate work in the background Example: A sales team can auto-update reports every morning without doing it manually. Big advantage: No coding needed. Big downside: It burns through usage limits FAST. If you work heavily with documents and dashboards all day, the basic plan disappears quickly. 3. Code = control + efficiency This is where most people get confused. Code is NOT only for developers. It’s for people who want: • more control • lower costs • better performance • custom workflows Example: No connector for your CRM? You can connect it yourself with a simple API. Need cleaner context? You can clear or compact chats instead of carrying huge conversations forever. Need faster dashboards? Run logic through code instead of loading everything into the chat. That’s the real difference: Chat → simple work Cowork → automated office work Code → scale, control, customization

If you’re building your first iOS app with AI, begin by choosing a real problem you want to solve. Keep things simple. Your first app doesn’t have to be large or complex. It just needs to work. Here’s a simple outline to follow: 1. Choose one clear problem to focus on. 2. Install Xcode on your computer. 3. Use your coding agent of choice. 4. Create the project in Xcode, then open it in your coding agent. 5. Install the Context7 MCP to help your agent quickly access the right documentation. 6. Plan and build one feature at a time. 7. Double-check your approach before you start building. 8. Work quickly, but make sure to keep your project organized. The most important thing in iOS development is to use standard iOS patterns. The AI will use custom patterns on its own, so I would recommend always just pointing back to the documentation for introducing a new feature. Most iOS apps use Swift. Follow best practices, separate your code into clear sections, and keep your files organized as you build. The AI agent will do this for you as long as you ask. AI can help you move quickly, but if the foundation is messy, the app gets harder to fix later. Once it works, you have two options: If you have an Apple Developer account, you can export and distribute it through the App Store. If not, you can still export it locally and use it as a private app. Start small. Build one useful thing. Then improve it. My latest app is called Megaphone. Released a month ago, doing 4-figures MRR. https://apps.apple.com/us/app/megaphone-audio-teleprompter/id6759921971 It’s a scriptwriter and video recorder for short-form videos that records your videos and removes silences. I learned a ton along the way, so if you have any questions, let me know.

Hey everyone! Frame looks to be forcing th V4 update on everyone, but I know there were issues with the KEDB Extreme last year moving it from v3 to v4. I'm looking for some alternatives to Frame.io as a hosting platform for images and videos (and one that can preferably slide in easily to all the old automations🤣) Didn't know if there was anyone in here who had already made the switch? I had been looking at using Cloudfare R2 to get a public URL, but would be welcome to any uggestions