Request in ordinary language
Type a reminder, calendar, message, or email request without navigating a detailed form.
Clarify
A native iPhone assistant that turns natural-language requests into bounded reminders, calendar actions, and communication drafts.
- Category
- Small Intelligences
- Platform
- iPhone · iOS 17+
- Status
- Active development
Natural language without invisible authority.
Every request passes through normalization, validation, clarification, confirmation, permission, and execution rules. Drafts remain unsent, and optional model-assisted interpretation never decides what the app is allowed to do.
User value
Ask naturally. Keep control.
Spend less time filling forms without hiding what the assistant understood or will do next.
Review consequential steps
Missing details, ambiguous contacts, permissions, and calendar confirmation remain visible.
Keep communication unsent
Message and email outputs stay as drafts that can be reviewed, rewritten, and copied.
Features
A deliberately bounded assistant.
Clarify supports a small set of actions it can validate and explain.
- 01
Create reminders
Ask for missing dates, request access in context, and return a structured result summary.
- 02
Create calendar events
Show the interpreted title and timing, then require confirmation before creation.
- 03
Resolve contact ambiguity
Present stable choices when more than one contact matches a name.
- 04
Prepare communication drafts
Create message and email previews without an automatic sending integration.
- 05
Rewrite within limits
Make a draft shorter, more polite, or more direct while preserving its preview-only state.
- 06
Use Apple Shortcuts
Hand a request into the app and process it through the same visible policy path.
How it works
Interpretation earns its way to action.
Flexible language and deterministic policy remain separate.
- 01
Request
Type in Clarify or hand text in from Apple Shortcuts.
- 02
Interpret
Use a deterministic fast path or optional on-device model assistance when available.
- 03
Normalize
Turn the result into a supported intent with explicit parameters and requirements.
- 04
Clarify
Resolve missing details, ambiguous names, permissions, or unsupported scope.
- 05
Confirm
Review a consequential action before the matching platform service is called.
- 06
Act or prepare
Create a reminder or event, or return an unsent communication draft.
Product demos
The bounded flow in motion.
Clarify interface demo
12 secInterface
The safeguards are visible.
These simulator captures use deterministic fixtures inside the real app interface. They demonstrate presentation states, not live platform actions.
View full size
Ask before it acts
Begin from a quiet conversation surface with a clear request field.
View full size
Create reminders
Return a concise result summary with the reminder title and due date.
View full size
Review calendar events
Expose the interpreted event details before creation.
View full size
Clarify names
Ask the user to choose when several contacts match.
View full size
Draft without sending
Keep the email preview and the not-sent boundary together.
View full size
Explain the safeguards
Show model availability and the deterministic checks that remain in control.
View full size
Rewrite safely
Offer bounded tone changes without turning the draft into a sending action.
Product concept
Language is a proposal, not permission.
Natural-language convenience becomes trustworthy when interpretation and authorization remain distinct.
Models do not authorize
Deterministic product policy decides whether Clarify asks, confirms, requests access, prepares, acts, or stops.
Uncertainty stays visible
Missing information and ambiguous names become explicit interface states rather than silent guesses.
Autonomy has a boundary
The app creates supported reminders and confirmed events. Communication remains preview-only.
Architecture
Probabilistic interpretation. Deterministic action.
Native services remain behind one runtime policy path, whether the request comes from the app or Shortcuts.
- 01Typed or Shortcut request
- 02Deterministic or model-assisted parser
- 03Intent normalization
- 04Validation and decision policy
- 05Clarification, confirmation, or permission
- 06Native service or draft preparation
- 07Visible result summary
Local-first boundary
No app networking, cloud model, analytics, telemetry, database, or durable conversation store appears in the current source.
System-owned persistence
Completed reminders and events use Apple stores. Conversation, task, and draft state remain in memory.
One policy path
Shortcut input cannot bypass the in-app validation, permission, confirmation, and execution rules.
Technology
Native services behind explicit policy.
Application
- Swift
- SwiftUI
- iOS 17+
Interpretation
- Deterministic parser
- Apple Foundation Models when available
- Structured normalization
Platform
- App Intents
- EventKit
- Contacts
- Shortcuts
- Clipboard
Validation
- XCTest
- Dependency injection
- Accessibility metadata
- DEBUG-only fixtures
Development
Core v1 flows are implemented.
The native application and its bounded workflows are working and extensively tested. TestFlight status, final media approval, and physical-device accessibility acceptance remain unresolved.
- Stage
- Active development
- Automated suite
- 444 tests passing
- Platform
- iOS 17+
- App networking
- None
Implemented
- SwiftUI conversation interface with visible clarification, permission, confirmation, draft, result, and trust states
- Deterministic parsing with conditional Apple Foundation Models interpretation and fallback
- Reminder and confirmed calendar-event creation through EventKit
- Contact resolution with explicit selection for ambiguous names
- Preview-only message and email drafts with copying and bounded rewrites
- Ask Clarify App Intent, Shortcuts handoff, accessibility metadata, and release-gated diagnostics
Release focus
Reconcile release configuration and documentation, complete the owner-controlled TestFlight path, finish physical-device VoiceOver and large Dynamic Type acceptance, and approve the public media set.
Clarify lab notes
The project, over time.
Notes about the thinking, architecture, development, and decisions behind this work.
-
Clarify
3 Jun 2026 · DraftMaking Trust Visible
Clarification, permission, confirmation, draft, and result states turned internal safety policy into an interface a person could inspect.
-
Clarify
30 May 2026 · DraftFrom Language to Bounded Actions
A flexible interpretation layer became useful only after deterministic validation and policy could decide what was permitted next.
-
Clarify
23 Apr 2026 · DraftNative Foundations
Early separation between interface, infrastructure, runtime, and services created the foundation for a testable bounded assistant.