SCOPE
Start with the calendar.
A focused source of context and a problem people can recognize.
LyraRelease candidate
A calendar with something useful to say.
I narrowed a broad assistant thesis to useful calendar guidance. Recommended meeting times become Calendly availability only after the person reviews and approves them.
- My role
- FOUNDER & SOLO BUILDER · NATIVE iOS · PRODUCT STRATEGY TO RELEASE PREPARATION
- Scope
- Product strategy, native iOS design and engineering, and release preparation.
- Key decision
- Focus a broad assistant thesis on calendar guidance; require explicit approval before publishing availability.
Context
The original vision was wider than the first useful product.
Lyra began as a broad assistant thesis. I narrowed it to the calendar, where the product could give useful feedback immediately and make its judgment visible.
The central problem became practical: understand where commitments put the week under pressure, then help a person decide what can fit without giving away control.
VALUE
Say something useful.
Surface one actionable judgment, or explain that nothing needs attention.
OWNERSHIP
Build the whole path.
Connect the product thesis to a native interface, integration, and release foundations.
Insight
A recommendation needs a clear permission boundary.
Knowing when a meeting could fit does not grant permission to change availability. The person must be able to see the proposal and decide what becomes bookable.
That boundary shaped the product: local calendar analysis, explicit confirmation for Calendly changes, and feedback that distinguishes a saved rule from an actually bookable start.
LOCAL CONTEXT
Read the week.
Core calendar analysis stays on device. Apple Calendar remains read-only.
EXPLICIT CONTROL
Approve the change.
Select the meeting starts and confirm the availability to publish.
VERIFIED FEEDBACK
Explain the result.
Distinguish provider rules that were saved from starts the booking page can offer.
Decisions
Turn a useful insight into availability people choose to publish.
The latest native shortcut lets people select recommended starts from the week view, review the proposed change, and publish directly to Calendly.
Before publication, Lyra rechecks calendar conflicts and provider settings. Publishing changes availability; it does not book an invitee.
01 / READ
Understand the week.
Analyze local commitments and the current scheduling boundaries.
02 / RECOMMEND
Find viable starts.
Offer starts that fit calendars on the device within the chosen horizon.
03 / REVIEW
Choose what changes.
Select one or more starts and explicitly confirm publication.
04 / PUBLISH
Check the result.
Recheck conflicts and return a clear provider receipt.
Impact
Production publishing is verified. Adoption is the next test.
Calendly publication was verified on a physical iPhone and checked on the public booking page. The direct-selection shortcut followed in the next native iteration.
The latest release candidate includes English and Brazilian Portuguese, consent boundaries, secure sessions, data export and deletion, and support foundations.
What changed, and where
What the product demonstrates
Founder ownership connected a focused product thesis to a native experience and a verified production integration.
01
User control
Implemented product behavior
Recommendations led to an explicit decision.
- People review the meeting starts they want to publish.
- Apple Calendar stays read-only; Calendly availability changes require confirmation.
02
Delivery
Verified integration
A real publishing path was verified.
- Calendly publication was tested on a physical iPhone and checked on the public booking page.
- The direct-selection shortcut followed in the next native iteration.
03
Founder ownership
Release candidate
The product reached a native release candidate.
- Strategy, interaction design, native implementation, and integration formed one delivery path.
- Release preparation includes English and Brazilian Portuguese, consent, secure sessions, data controls, and support foundations.
Distribution, adoption, time saved, retention, and commercial traction remain to be established.
