How much time will I actually save with Fazm?

Most users report saving 45-90 minutes per day on repetitive tasks. The biggest time savings come from email management (drafting replies, sorting, archiving), form filling (expense reports, CRM updates, applications), research (comparing products, gathering data from multiple sites), and social media (cross-posting, scheduling, replying). For example, booking a flight that normally takes 10 minutes of clicking through airline sites takes a single voice command with Fazm. Filing an expense report that requires opening a PDF, extracting numbers, and entering them into a spreadsheet becomes one spoken sentence. The more repetitive and multi-step your daily work is, the more time you get back.

What exactly can Fazm control?

Fazm controls everything you can do manually on your Mac. That includes mouse movements and clicks, keyboard typing, browser navigation and form filling, app switching, file management in Finder, and system-level actions. It uses direct browser DOM control for web interactions - meaning it reads and manipulates the actual page structure rather than taking screenshots and guessing where to click. For native macOS apps, Fazm uses accessibility APIs to interact with buttons, menus, text fields, and other UI elements. This works across any application: Chrome, Safari, VS Code, Slack, Figma, Terminal, Mail, Calendar, and more.

How is Fazm different from ChatGPT or Claude?

Chatbots like ChatGPT and Claude give you answers in a conversation window. Fazm takes action directly on your computer. When you say 'reply to Sarah's email,' Fazm opens your email app, finds Sarah's message, writes a contextual reply, and sends it. A chatbot would tell you what to write, but you still have to do all the clicking and typing yourself. Fazm moves your mouse, types on your keyboard, clicks buttons, and navigates between apps. It is a computer agent, not a chat assistant.

How does the memory layer work?

Fazm builds a personal knowledge graph by extracting information from your files, browsing history, conversations, and daily activity. Over time, it learns your contacts (names, emails, relationships), accounts and credentials, preferences (formatting, tone, scheduling habits), and frequently used workflows. In your first week, you might say 'Reply to Sarah's email, she's my cofounder, her email is sarah@acme.com.' By week four, you just say 'Reply to Sarah' because Fazm already knows who she is. By week eight, Fazm can draft the reply before you even ask. All of this data stays locally on your Mac - your knowledge graph never leaves your machine or gets sent to any cloud service.

Is Fazm safe? Can it mess up my computer?

Safety is built into every layer of Fazm. You watch every action in real-time on your screen - Fazm moves your mouse and types visibly, so there is nothing hidden. You can stop any action at any point by pressing a keyboard shortcut. Fazm also shows you what it plans to do before executing destructive actions like deleting files or sending emails, giving you a chance to confirm or cancel. Because Fazm is open source, the code is fully auditable on GitHub. There is no hidden behavior, no background processes making changes you cannot see, and no actions that bypass your screen.

What platforms does Fazm support?

Fazm currently supports macOS, running natively on both Apple Silicon (M1, M2, M3, M4) and Intel Macs. It is built with Swift and uses macOS-specific frameworks like ScreenCaptureKit for screen analysis and Accessibility APIs for app control, which is why macOS is the primary platform. Windows and Linux support are on the roadmap but do not have release dates yet. You can also control your Mac remotely from your phone using Fazm Remote, which gives you voice access to your desktop while you are away from your computer.

How does Fazm voice input work?

One keyboard shortcut activates push-to-talk. Hold the key, speak naturally about what you need done, and release. Fazm transcribes your speech locally using on-device models, so there is no network latency for the voice recognition step. You do not need wake words like 'Hey Siri' or 'OK Google' - just press and talk. You can also type commands into the floating toolbar if you prefer text input. Fazm understands natural language, so you do not need to memorize specific commands. Say 'book me a flight to Tokyo next Thursday' or 'find the cheapest AirPods on Amazon' and Fazm figures out the steps.

Is my data sent to the cloud?

Fazm processes screen analysis and memory entirely on your machine. The personal knowledge graph, file indexing, and screen capture all run locally. The only data that leaves your Mac is the intent - a text description of what you want to accomplish, which is sent to the AI model (Claude or GPT) for action planning. Your actual screen content, file contents, browsing history, and personal knowledge graph never leave your computer. Fazm is also open source, so you can verify exactly what data is transmitted by reading the code on GitHub. For users who need complete air-gapped operation, local model support is planned.

Building a Production iOS App in 35 Hours with Claude Code

Fazm Team·March 17, 2026·3 min read

claude-code ios swiftui swift app-development production styling

Building a Production iOS App in 35 Hours with Claude Code

Building a production app with Claude Code is a real thing now. But the experience is not what most people expect. The logic, API integrations, data models, and even the architecture come together fast. The part that eats all the time is styling.

What Goes Fast

Claude Code handles the structural work incredibly well. Setting up a SwiftUI project, defining data models, wiring up networking layers, implementing business logic - this is where AI coding shines. You describe what you want, the agent writes it, and it mostly works on the first pass.

The same applies to macOS apps. Building Fazm's SwiftUI frontend with a Rust backend, Claude Code handled the cross-language integration, the FFI bridge, and the data flow. The hard problems were not the hard problems.

SwiftUI Styling Is the Real Boss Fight

The moment you try to make things look polished, everything slows down. SwiftUI's layout system is powerful but opinionated. Getting precise spacing, custom animations, responsive layouts that work across screen sizes - this is where Claude Code starts producing output that looks "almost right" but needs constant iteration.

The feedback loop becomes: generate, preview, adjust prompt, regenerate, preview again. Each cycle is fast, but there are dozens of cycles per screen. Pixel-perfect design requires a level of visual judgment that LLMs do not have yet.

Practical Tips

A few things that help speed up the styling phase:

Use a design system with predefined spacing, colors, and typography tokens
Show Claude Code screenshots of what you want and what it produced
Break screens into tiny components so each iteration scope is small
Accept "good enough" for the first version and polish later

The 35-Hour Breakdown

Roughly 10 hours went to architecture and logic. Around 5 hours to testing and debugging. The remaining 20 hours were spent on making it look and feel production-quality. That ratio - 60% on styling - surprised everyone who tried it.

The takeaway is not that AI coding is slow. It is that the bottleneck has shifted from "can I build this" to "can I make this beautiful."

Fazm is an open source macOS AI agent. Open source on GitHub.

Building a Production iOS App in 35 Hours with Claude Code

Building a Production iOS App in 35 Hours with Claude Code

What Goes Fast

SwiftUI Styling Is the Real Boss Fight

Practical Tips

The 35-Hour Breakdown

More on This Topic

Related Posts

Best Practices for Shipping iOS and macOS Apps with Claude Code

AI Coding Technique: Change One File, Migrate the Entire Codebase

Claude Code for Swift/macOS Development - ScreenCaptureKit and Deprecated APIs