Apple built a volume knob. You needed a schedule. Conduct is built on the premise that a person's day has a shape, their relationships have a structure, and any system worthy of managing their attention must understand both.
It does not just dim noise. It understands when different people and channels should matter, then carries that logic across the system.
Adaptive Attention Model
Apple's notification system was built around device states — not around how people actually live. Focus, at its core, is a volume knob disguised as a feature: it offers degrees of contact without any coherent theory of why those interruptions should or shouldn't happen. The categories don't flow with the rhythm of a human day, and there's no system underneath — no morning, no evening, no sense of who matters when.
Focus — Apple Settings
Driving. Gaming. Sleep. Work. In that order.
Focus categories appear in no particular order. There's no Morning. No Evening. No Weekend. A sleeping person and a working person are just two points on a dial.
Focus — Allowed Apps
Decide per app. Not per person.
Messages, Telegram, Instagram, Slack. All toggled independently. There's no way to say: allow this person in whatever channel they use, because the system has no model of human relationships at all.
Focus — Notification Options
10 settings. Zero theory.
Every box is tweakable, app by app. But there's no design philosophy underneath — no theory of how a real person would actually want to live with this. It's digital assembly, not purposeful design.
This is a digital volume control,
not a noise filtration system.
A conductor doesn't silence the orchestra. They shape it — deciding which instruments play, when they come in, at what volume, and for how long. Conduct applies that same logic to every person and app competing for your attention.
Different moments of a day deserve different qualities of information.
Apple Focus
Arbitrary order. No logic.
Conduct™
Chronological. Always.
Human language, human purpose
Not app toggles and notification types — set up the way a person thinks about their day, not the way a developer thinks about device states.
Cohesive access tiers
People are grouped by relationship, not app. One decision per person covers every channel — calls, messages, and email at once.
Chronological, always
Time blocks run in the order the day actually unfolds — Morning to Work to Evening to Sleep. No arbitrary ordering, no mode-switching.
Contact-first, device-wide
Set access for a person once. The Conduct API pushes that decision to every messaging app on your device — automatically.
Design Principle
"Conduct should never feel like configuring software. It should feel like explaining your life to someone who is genuinely trying to help you protect it."
Setup doesn't begin with toggles. It begins with a visual question: "Tell us a little about your day." The user sees a circular clock-face interface — a draggable ring — and shapes it to match how they actually live.
Personal time before work begins. Close contacts only — a quiet start before the day opens up.
Professional tier. Colleagues, clients, and critical family — the people whose calls genuinely can't wait.
Social and family time. The widest personal access of the day — the people you actually want to hear from.
Near-total filter. Only true emergencies from a carefully chosen handful of people break through.
After weekday setup, Conduct asks if your weekend looks different — and offers an identical ring to adjust or copy from.
Tap any segment of the ring to mark it as personal time. These blocks layer on top of any existing structure.
9-to-5 Weekday, Shift Worker, and Freelance Flexible — pre-populated Day Objects for users who want a starting point.
Drag any white boundary handle to resize a block. Tap a segment to select it. Use + to add a block, − to remove the selected one.
With your Day Object set, Conduct walks through each time block in chronological order and asks two questions: who should reach you, and how? Access is organized into three tiers — the system reasons for you, building from what you've already told it.
If someone earns call access, they automatically earn message and email access too. Higher tiers inherit lower-tier permissions. You never select the same person twice.
Access Matrix — Sample Configuration
Hover any badge to see which channels are included.
"Set access once at the top. Everything below it falls into place."
Five principles run underneath every decision Conduct makes. Pick a scenario below and watch the cascade evaluate it in real time.
Whitelist-First
Default is silent. Every access is granted explicitly — never revoked from full. Focus starts open; Conduct starts closed.
Access Implies Access
Call access automatically includes messages and email. One decision covers all channels — no per-app drift.
Daytime Adds, Nighttime Subtracts
Morning→Work asks who to add. Evening→Sleep asks who to remove. The question direction follows the shape of the day.
People Before Apps
Contact permissions are set once. The Conduct API pushes those whitelists to every registered app. The OS becomes the single source of truth.
Smart Defaults
On first launch, on-device analysis of call and email history pre-suggests Tier 1 contacts. You confirm or adjust — never start cold. Nothing leaves the device.
Trace a Notification
← Select a scenario to trace
"The system asks the right question at the right moment — so you never have to think about what you forgot."
The settings screen replaces Focus entirely. Tap any block below to drill into its detail view — the same navigation hierarchy a user would experience on device.
iOS Settings View — Tap any block to explore
Your Day — Wednesday
Quick Quiet
Apps — Work
Quick Quiet
Apps — Work
Design Decisions
Always Chronological
Morning. Work. Evening. Sleep — always in time order. Never alphabetical, never arbitrary.
Categories, Not Lists
Three app buckets replace forty individual toggles. One decision covers every app in each category.
Dial for Time Nudges
A round dial bumps any block boundary in 15-min increments — no re-entering setup required.
Status Bar Presence
The active block name lives in the status bar — replacing the Focus dot with something meaningful.
Tap any block in the mock
Drill into tier breakdowns and app settings — the same hierarchy a user navigates on device.
Conduct isn't an island. One decision here propagates to every communication app on the device — instantly, silently, automatically.
API Propagation
Smart Contact Lists
Every person assigned to a Conduct tier is automatically added to a labeled smart list in Contacts. Adjust a tier — their membership updates instantly across every app that uses Contacts.
In-Card Access Control
Open any contact card and a "Conduct Access" row shows their tier across every block — editable directly from within the card, without opening Settings.
The Conduct API
WhatsApp, Signal, Slack, Teams — any registered app receives the current whitelist the moment a block activates. The OS becomes the single source of truth. Apps don't need to know about each other.
"Set it once in Conduct. Every app on your device follows."
Not every need for silence fits neatly into a time block. Quick Quiet is a one-tap override that drops all notifications for a set duration — then hands control back to your schedule automatically.
Accessible from Lock Screen, Control Center, and Conduct settings — wherever you are when you need quiet.
Five timer options from 15 minutes to indefinite. The "Until I End It" option is for the times you can't predict when you'll be ready.
When the timer ends, your normal block rules resume. No action required. The system just picks up where it left off.
Pause for how long?
Ten dimensions. Zero configuration overlap.
What a completed configuration looks like — and how it behaves when the day actually unfolds.
The day as it unfolds
Partner texts. Morning block, Tier 1 — comes through immediately. Colleague group chat arrives at the same moment. Tier 2 for Morning: stays silent until 9am.
Work block activates. The colleague group chat that was held since 6:45am delivers its queued notifications. You read them when you're ready — not when they arrived.
Child's school calls mid-meeting. School is Tier 1 for Work — it rings even with ringer silenced. You assigned it this tier because it genuinely cannot wait.
Unknown number calls. Not in any Work tier. Conduct silences it — no ring, no vibration, no badge. Goes straight to voicemail without interrupting your afternoon.
Evening activates. The day's queued notifications arrive — the afternoon Slack threads, the newsletter, the group chat from this morning. All at once, on your terms.
Sleep activates. Only three contacts can call. Everything else is completely silent until morning. The system didn't ask you to manage anything — it just did what you told it your life looked like.
"The system didn't ask the user to manage their notifications. It asked them to describe their life — and then managed the notifications for them."
Conduct isn't a hypothetical. It's what happens when design starts from the human and works outward — not from the technology inward.
The notifications stop. The day begins to feel like yours again. MMWB builds software in every category with that same instinct: the kind users don't just prefer, but can't imagine going back from.
How we work
Start from the human.
Every brief starts with behavior, not requirements. We ask what the user actually experiences before we ask what the product should do.
Work outward.
The system is designed from the inside out — logic first, interface second, technology last. It keeps the experience coherent under pressure.
Ship something leagues ahead.
We don't optimize existing patterns. We find the version users didn't know was possible — then make it inevitable.
Start a conversation.
Tell us what you're building, where the experience is breaking down, or where the idea still feels fuzzy. We'll bring the same level of clarity, structure, and product thinking you just saw on this page.
Common starting points