Software product company.

Engineering / Product notes

Behind
the interface.

The design decisions in each product, based on documented behavior. Each note separates what is documented from what is our interpretation.

01 / QuinScoutProduct design note

Designing for a stopping point.

A finite reading experience changes the interface. Five stories create a visible unit of progress, while source links let depth remain a choice. A refresh starts another set instead of extending an endless feed.

What the product documents

  1. 01

    Set the perspective

    Interests and a briefing profile give each selection context.

  2. 02

    Bring coverage together

    The product describes grouping duplicate coverage into one story.

  3. 03

    Explain the relevance

    Concise summaries pair the development with why it matters.

  4. 04

    Keep the source visible

    Original links and source-grounded follow-ups support deeper reading.

The evidence boundary

The public site describes duplicate grouping and relevance selection. It does not establish the internal infrastructure, model stack, ingestion volume, or latency. Those details are not claimed here.

QuinScout product guide ↗Public iPhone listing ↗
Explore QuinScout
02 / Visa WingmanProduct design note

Represent the journey, not the outcome.

A checklist turns preparation into visible work. The critical distinction is between a completed task and an external decision. Progress can describe organization; it cannot promise what a visa authority will decide.

What the product documents

  1. 01

    Define the journey

    Origin, destination, and purpose shape a preparation route.

  2. 02

    Organize the tasks

    A structured checklist separates document categories and next steps.

  3. 03

    Review the signals

    Preparation signals describe the documents, not the chance of a visa approval.

  4. 04

    Verify officially

    Source links and review labels keep the official authority in the loop.

The evidence boundary

These notes describe the published preparation experience and source-review labels. They do not assert a private readiness algorithm, document-encryption design, or immigration eligibility model.

Visa Wingman product and source boundaries ↗Public iPhone listing ↗
Explore Visa Wingman
03 / MasteryPulse CloudProduct design note

Offline is part of the experience.

When studying does not depend on a network, a short practice session can happen wherever time opens up. Local progress also sets an important expectation: another device does not automatically share the same learning history.

What the product documents

  1. 01

    Practice locally

    The learning experience works offline after installation.

  2. 02

    Record progress

    Progress, settings, and saved questions remain on the iPhone.

  3. 03

    Revisit a topic

    Adaptive Review prioritizes weak, due, and unseen topics.

  4. 04

    See the pattern

    Domain progress and objective coverage give study sessions context.

The evidence boundary

Offline operation, local progress, and review priorities are documented in the App Store listing. The specific storage engine, scoring weights, and scheduling algorithm are not public. The website quiz is an independent illustration.

Public iPhone listing and offline behavior ↗Original product support ↗
Explore MasteryPulse Cloud
04 / IrisProduct design note

Separate remembering from saving.

Keeping a conversation and using it in a later interaction are different choices. Making those choices distinct gives the person a more understandable boundary around a sensitive experience.

What the product documents

  1. 01

    Choose a starting point

    A check-in helps the person begin without perfect words.

  2. 02

    Choose the kind of help

    Listening, perspective, and practical help shape the conversation.

  3. 03

    Keep what is useful

    Saved conversations can be reopened or removed.

  4. 04

    Control future recall

    The public guide says recall is off by default and separate from saving.

The evidence boundary

The official site describes saved conversations, optional AI processing, and recall off by default. This is a discussion of that published interaction design, not a claim about clinical efficacy or the private processing architecture.

Iris experience and privacy controls ↗Iris availability and support ↗
Explore Iris

This website / Implementation notes

How this website
is built.

Content first.

Pages and product information are rendered on the server. The core story and links remain available before JavaScript loads.

Real interfaces, local state.

The phones on this site are recreations built in code from each app’s own design tokens and artwork. They hold temporary state in the browser and make no requests to product backends.

Accessible controls.

Native buttons, visible keyboard focus, labeled controls, and reduced-motion support keep exploration usable.