Aisle Seat One Back to our workLet’s talk
AS1 / Selected workBrand · Product · Engineering

The right details.
Nothing extra.

We built a deliberately simple product: choose the information to share, show a QR code and get back to the conversation. No account or hosted contact backend is needed for the core experience.

An AS1 product, from zero to one.
Strategy, identity, design and implementation.

Explore the work

Jekkil website

Jekkil marketing website and browser-local contact sharing tool

The website explains selective sharing and offers a browser-local QR tool.

Contact sharing mobile layout

Jekkil real React Native components showing synthetic quick links and contact cards

Quick Links, an Info Bank and reusable Contact Cards, without a sign-up flow.

The website explains selective sharing and offers a browser-local QR tool. Illustrative product content.
Our scope
Brand, product, design & build
Ownership
AS1, from zero to one
Platforms
iOS, Android, tablets & website
Foundation
Expo + local storage + QR

01The opportunity

One person. Different contexts.

At a party, a social profile may be enough. At a meeting, a portfolio and email make more sense. Sharing a complete contact record every time gives away more information than the moment requires.

We separated individual Quick Links, a reusable Info Bank and context-specific Contact Cards. The product hypothesis is that selective sharing can be fast without requiring either person to create an account.

The design question

How could we make sharing immediate while keeping the choice of information with the person sharing it?

01

Keep your details

Store reusable information on your device.

02

Choose a context

Use a Quick Link or a saved Contact Card.

03

Pick the fields

Share only what belongs in this moment.

04

Show a QR

The recipient uses their camera and normal contact support.

02From zero to one

One connected
scope of work.

We shaped the idea, created its identity, designed the experience and built the system that makes it work.

Selective, on-device sharing. The product choices, visual language and architecture developed together. Our research combined product, domain and technical exploration to shape the decisions below.

  1. 01

    Ideation & scope

    We focused on the moment of exchange and removed account creation, social feeds and hosted contact management from the core product.

  2. 02

    Technical research

    We worked through QR readability, vCard compatibility, character encoding and device sharing behavior before broadening the feature set.

  3. 03

    Brand identity

    We explored wordmark typography and a reciprocal face-and-hands symbol, then built a mint, cream and pale-yellow visual system.

  4. 04

    UX & visual design

    We designed Quick Links, an Info Bank, selective cards and a large QR sheet, with editable colors and contrast-aware rendering.

  5. 05

    Frontend engineering

    We built the Expo and React Native app with local persistence, vCard generation and QR SVG rendering for iOS and Android.

  6. 06

    Architecture & delivery

    We deliberately omitted a contact backend. A separate website and browser-local QR tool support discovery and lightweight sharing.

A complete brand identity

Recognizable.
Built to be used.

We made a privacy-conscious utility feel social and immediate. A distinctive symbol, friendly type and a small visual vocabulary keep the product approachable without adding complexity.

We created a connected identity system: logo, character, color, typography, iconography and interface patterns, then carried it into the website and distribution materials.

Jekkil’s reciprocal face-and-hands brand symbolJekkil wordmark
#00D9A5#FFF0A6#FFFEF8#29262F
Original identity artwork and a selection of the product’s color language.
Logo & wordmark
The reciprocal face-and-hands symbol suggests exchange. A Nunito Black wordmark gives it a soft, memorable signature that works as an app identity and a marketing phrase.
Character of the brand
Jekkil uses the symbol as its character rather than a large mascot family. The voice is conversational and built around the real moment of sharing.
Color system
Mint, cream and pale yellow create a light canvas, with deep green for identity and strong actions. Card customization adds personal expression while contrast-aware QR rendering protects scan readability.
Typography
Nunito Black 900 defines the wordmark. Plus Jakarta Sans supplies the app and website interface, with consistent weights for headings, details and controls.
Icons & components
Original line icons identify different information types. Rounded cards, restrained shadows, simple controls and a large QR sheet make the sharing action the visual priority.

03Product judgment

The choices
behind the experience.

What we chose, why it mattered and what it cost.

01 / Architecture by subtraction

A useful app can have no backend.

The core sharing flow does not need accounts, a hosted contact database, recipient tracking or an external service API. Contact information and saved cards stay on the device. A QR can carry a vCard directly.

The tradeoff

There is no cloud contact backup or automatic account-based device sync. That is a conscious scope choice, not an unfinished backend.

The implemented flow, simplified

  1. Choose locally

    Read only the fields selected for this card.

  2. Generate a vCard

    Encode the chosen contact information.

  3. Render a QR

    Make the payload scannable with suitable contrast.

  4. Share directly

    The recipient opens the data without a Jekkil account.

Product interaction and engineering are designed together.

02 / Selective sharing

The moment decides what to share.

Quick Links handle a single destination. The Info Bank keeps reusable fields. Contact Cards combine a chosen subset for a context. We designed the selection step to make the privacy decision visible before the QR appears.

The tradeoff

Selection adds one small decision. Reusable cards keep repeated exchanges fast without exposing everything by default.

QR sharing

Jekkil QR sharing drawer carrying a fictional contact vCard

The selected card becomes a scannable contact payload.

The selected card becomes a scannable contact payload.
03 / Brand & interoperability

Friendly on the surface. Careful underneath.

A warm identity makes the interaction approachable. Underneath it, UTF-8 vCard handling preserves names in non-Roman scripts, device-aware contact formatting supports recipients, and automatic contrast keeps customized QR codes legible.

The tradeoff

A small interface still needs substantial compatibility work. Simplicity is the result of those decisions.

Wordmark exploration

Original Jekkil wordmark font comparison design artifact

An original identity exploration, before the final wordmark choice.

An original identity exploration, before the final wordmark choice.

04Platforms & architecture

Small scope. Complete execution.

Expo and React Native share the native application across iOS and Android, including larger tablet layouts. Local storage, QR generation and vCards cover the core flow.

We did not add Supabase where the product did not need it. There is no Jekkil sign-up or server-side contact database.

Core QR contact sharing works offline. Linked websites still need a connection. Optional store purchases and native image / share APIs exist, so the whole app is not literally integration-free.

Website

Jekkil website

Jekkil marketing website and browser-local contact sharing tool

The website explains selective sharing and offers a browser-local QR tool.

The website explains selective sharing and offers a browser-local QR tool.
Tablet

Contact sharing tablet layout

Jekkil actual source interface rendered in a tablet-sized web preview

The shared native components organize the same local information on a wider screen.

The shared native components organize the same local information on a wider screen.
Mobile

Contact sharing mobile layout

Jekkil real React Native components showing synthetic quick links and contact cards

Quick Links, an Info Bank and reusable Contact Cards, without a sign-up flow.

Quick Links, an Info Bank and reusable Contact Cards, without a sign-up flow.

October 2026 source-component captures with synthetic contact details in reserved example domains. Mobile and tablet previews render the actual native components through React Native Web; they are not native-device screenshots. The web image shows the separate website.

01

On-device details

A local Info Bank supplies selected fields.

02

Local generation

The app creates the contact payload and QR.

03

Direct exchange

The recipient opens it using normal device tools. No contact server is in the path.

The working stack

Design meets
implementation.

Jekkil technology stack and purpose
LayerToolsPurpose
Native experienceExpo · React Native · TypeScript · React NavigationShared native screens, cards and QR interaction.
Local dataAsyncStorage · Expo SecureStore / Crypto · AESOn-device persistence and encrypted saved information, with environment-dependent key storage.
SharingvCard · QR SVG · Native share / image APIsDirect contact payloads and readable, customizable QR codes.
Website & commerceReact · Vinext · Vite · Apple / Google billingSeparate marketing and browser-local QR experience; optional native purchases.

Security is product work

Useful also
means responsible.

For Jekkil, the strongest security decision is reducing the data and services the product needs. We do not claim a SOC 2 assessment, attestation or certification for this local-first app.

SOC 2 is an independent examination of an organization’s controls against trust services criteria. Aligned controls and readiness work do not equal an auditor’s SOC 2 report, and “certified” would misstate our status. About SOC 2

Less data to collect

No hosted contact database, account requirement or recipient tracking in the core flow.

Explicit disclosure

The user chooses the fields a QR reveals. A visible QR is itself a shareable payload.

Local safeguards

Saved information uses encrypted storage. Key protection depends on the available device and runtime; we do not claim audited encryption.

05Brand, marketing & distribution

The website is
part of the product.

We carried the selective-sharing identity into concrete situations: a social profile, a work card or just the information this moment needs.

We connected identity, messaging, product education and acquisition. Conversion means helping the right visitor reach the next useful action, then measuring whether that action leads to value.

Visit the Jekkil website

Jekkil website

Jekkil marketing website and browser-local contact sharing tool

The website explains selective sharing and offers a browser-local QR tool.

The website explains selective sharing and offers a browser-local QR tool.

Search discovery

Use-case guides and a browser-local vCard QR tool offer useful search destinations. Page metadata, canonicals, schema and a sitemap support discoverability.

Conversion design

The website demonstrates the exchange, explains that recipients need no account, and keeps App Store and Google Play entry points close to the product promise.

Platforms & stores

Native store listing copy, screenshots, localization and website download routes communicate the same small, clear product. A free web tool also lets visitors experience contact QR generation directly.

From discovery to first value

01

Find a sharing need

Arrive through a guide or the QR tool.

02

See it work

Understand selective cards and direct scanning.

03

Choose the native app

Download for iPhone or Android.

04

Share immediately

Create a card and show a QR without sign-up.

We would measure tool use, store-entry clicks, successful QR exchanges and repeat sharing. Optional paid customization needs its own demand validation.

06Delivery & learning

A working product.
An open hypothesis.

We delivered the product system described here. Product-market fit has not been established.

These case studies show our ability to connect brand, product, design and engineering. The next stage is to establish adoption, paid demand and customer outcomes.

0

Accounts required

For the core contact-sharing experience.

0

Contact servers

QR payloads are generated on the device.

0 → 1

Complete product

Identity, experience, native engineering and website.

What the build taught us

One lesson worth carrying forward.

Full-service delivery includes deciding what not to build. A smaller architecture can reduce operational burden while making the experience faster and easier to explain.

The next validation

Does the product earn its place?

We need to validate repeat use in real exchanges, QR success across recipients’ devices and demand for paid customization. A deliberately small architecture does not establish market fit by itself.

The right team for the stage

Start focused.
Grow the responsibility.

We can take a product from idea to a working release, including its brand, frontend, managed backend and integrations.

The team model should evolve with the risk and demands of the business.

Early validation

AS1 leads the build.

Before market fit is proven, scope and direction change quickly. Where appropriate, Supabase gives us a practical managed foundation. We can own application data models, authentication, backend functions and integrations while iterating on the product.

Established fit & fast growth

Add a dedicated engineering lead.

We recommend a lead responsible for data architecture, backend reliability, infrastructure and cybersecurity, working with AS1 on brand, product and design. Supabase may remain the right platform; scale calls for stronger engineering ownership, not an automatic rewrite.

Health-tech, fin-tech and other sensitive products: involve specialist engineering and security leadership from discovery. Data sensitivity, regulatory duties and operational risk can require that collaboration before market fit or rapid growth.

Your idea could be next

Let’s make
something useful.

Bring us the problem, the people it serves and the stage you’re at. We’ll help shape a focused path from idea to product.

Discuss your project
info@aisleseatone.com