Changelog

Product updates from the wamid team.

This changelog highlights the releases that move wamid closer to its mission : making personal memory easier to capture, safer to trust, and more useful over time.

It is not a raw engineering log. It is a curated product history for users, partners, and early supporters.

  1. v0.71.0Latest

    Memory becomes a home

    wamid's Memory page now brings notes, private items, reminders, and recent captures into one calm space.

    Highlights

    • New Memory filters : All, Recent, Private, With reminder.
    • Temporal grouping : Today, Yesterday, This week, Older.
    • Badges for audio, image, reminder, and private notes.
    • Manual Private flag to keep selected notes outside AI processing.
    • Ask receives a more polished thinking state.
    • EN, FR, and AR interface coverage aligned for the core experience.
    • RTL and accessibility improvements continue across the product.

    Why it matters

    Memory is no longer a storage list. It is becoming the place where wamid organizes what matters.

  2. v0.70.0

    wamid becomes a living memory product

    This release aligns wamid's identity, navigation, AI memory layer, and privacy foundation into a single product direction.

    Highlights

    • Littlab becomes wamid across product, brand, and interface.
    • New navigation foundation : Present, Upcoming, Memory, Ask.
    • Ask becomes a memory-first conversation space.
    • Source-backed answers begin inside Ask.
    • Mini AHA begins detecting repeated ideas and turning them into useful memory signals.
    • Wisp cards start bringing dormant notes back at the right moment.
    • The first Return Engine layer becomes visible.
    • Sensitive capture filtering is added across AI paths.
    • wamid's orange memory signal becomes the visual identity.

    Why it matters

    wamid stops being a set of features and becomes a clear product : a private memory system.

  3. v0.65.0

    Privacy-first AI infrastructure

    wamid's AI layer moves from experiment to infrastructure.

    Highlights

    • AI gateway deployed with zero-retention routing.
    • Structured AI responses prepared for reliable product actions.
    • Model routing prepared for fast and advanced reasoning modes.
    • Semantic memory search foundations added.
    • Embedding pipeline prepared for memory retrieval.
    • AI paths designed to remain swappable and provider-independent.
    • Sensitive data protection added before memory processing.

    Why it matters

    The model is not the moat. The trusted memory architecture is.

  4. v0.60.0

    The first Return Engine foundations

    wamid begins learning when something should come back.

    Highlights

    • Early dormant note detection.
    • First scoring model for memory value.
    • Initial Wisp logic for resurfacing useful notes.
    • Early "why this matters" signals.
    • Better note state tracking.
    • Better reminder context.
    • Quiet resurfacing experiments instead of aggressive notifications.

    Why it matters

    A memory product is not valuable because it stores things. It is valuable because it brings the right thing back.

  5. v0.55.0

    Present becomes the daily surface

    The home screen becomes calmer, more focused, and more useful.

    Highlights

    • Present screen foundation.
    • Golden Point state machine for daily memory signals.
    • Inline actions directly from home cards.
    • First emotional interface states : calm, ready, urgent, critical.
    • Material 3 Expressive foundation.
    • Warmer dark mode.
    • Orange used as a focused signal, not decoration.

    Why it matters

    The home screen stops being a dashboard and becomes a quiet stage for what matters now.

  6. v0.50.0

    Capture foundations

    Everything starts with capture.

    Highlights

    • Unified intake for text, voice, image, link, and share target.
    • Voice capture foundations.
    • Android share sheet support.
    • Early entity extraction for who, when, what, and where.
    • First capture sheet designed for fast, one-handed use.
    • Cleaner separation between raw input and useful memory.

    Why it matters

    If capture is slow, memory never starts.

  7. v0.45.0

    Reminder reliability

    wamid strengthens the first version of "bring this back later."

    Highlights

    • Alarm scheduling foundation.
    • Reminder recurrence support.
    • Notification channels for reminder importance.
    • Snooze and Done actions.
    • Boot recovery foundations.
    • Better overdue handling.
    • Cleaner reminder editing.

    Why it matters

    Trust starts with the quiet, boring things working every time.

  8. v0.42.0

    First impression and product craft

    The first impression gets the care it deserves.

    Highlights

    • Android 12+ splash foundation.
    • wamid mark visibility improvements.
    • Reusable shimmer states.
    • First brand motion details.
    • Reduce-motion support for loading effects.
    • Warm visual system begins to take shape.

    Why it matters

    A memory product should feel calm before it feels clever.

  9. v0.41.0

    Privacy hardening

    Privacy becomes part of the architecture, not just the promise.

    Highlights

    • Encrypted token storage foundation.
    • Safer authentication handling.
    • Local-first onboarding analytics.
    • AI usage gates prepared.
    • Sensitive capture handling begins.
    • Backup and restore foundations improved.

    Why it matters

    Private memory only matters if "private" is technically true.

  10. v0.35.0

    Notes start becoming memory

    Notes stop being flat text and begin carrying context.

    Highlights

    • Notes database foundation.
    • Basic note editing.
    • Note list and detail screens.
    • Early note metadata.
    • Local search foundations.
    • Private note direction begins.
    • Stronger offline-first behavior.

    Why it matters

    A note is not just text. It is a memory object waiting to become useful.

  11. v0.30.0

    Android-first foundation

    wamid commits to Android first.

    Highlights

    • Android application shell.
    • Compose UI foundation.
    • Room database foundation.
    • MVVM architecture.
    • Offline-first data model.
    • First reminder and note flows.
    • Early design system tokens.

    Why it matters

    Depth on one platform beats shallow noise across five.

  12. v0.25.0

    Daily loop prototype

    The first daily habit appears.

    Highlights

    • Early Today screen.
    • Basic reminder list.
    • Simple note capture.
    • First daily state experiments.
    • Basic completion flow.

    Why it matters

    The product begins looking for its daily reason to exist.

  13. v0.20.0

    Reminder core

    The first reliable "bring this back later" system.

    Highlights

    • Create reminder.
    • Edit reminder.
    • Mark as done.
    • Due dates and times.
    • Local notification foundation.
    • Overdue state.

    Why it matters

    Return starts as a reminder before it becomes intelligence.

  14. v0.15.0

    Capture prototype

    The first spark of wamid : write something down before it disappears.

    Highlights

    • Quick text capture.
    • Basic local storage.
    • Simple list of captured items.
    • First editing flow.
    • First delete and restore logic.

    Why it matters

    If capture is slow, memory never starts.

  15. v0.10.0

    First private build

    The first version that could be opened, used, and broken.

    Highlights

    • First Android shell.
    • First navigation structure.
    • First local persistence.
    • First private test install.
    • First product feedback loop.

    Why it matters

    The idea becomes something real enough to test.

  16. v0.1.0

    The seed

    Before wamid had a name, it had a frustration : important thoughts disappear too easily.

    Highlights

    • Personal memory concept.
    • Notes and reminders direction.
    • Android-first decision.
    • Privacy-first requirement.
    • Early thinking around Return before the Return Engine had a name.

    Why it matters

    wamid begins with one belief : memory should work with you, not wait for you to search.

About this changelog

This changelog is curated. It does not list every commit, migration, bug fix, or internal refactor. It highlights the product milestones that shaped wamid. For technical releases, we keep a separate engineering log. For users, this is the story of how wamid becomes more useful, more private, and more alive.

Want to shape the next release?

Lighthouse opens in small weekly waves. Join the private beta and help build the memory layer before public launch.