KEPLER WOLF LIMITED

Night chart

The chart has teeth.

Mobile products inked like a star chart: sharp peaks, a closed ring, and a path you can follow on iOS and Android.

Contact the studio Read the privacy note

01 — Platforms

Two arcs, one ring

KEPLER WOLF LIMITED has built mobile apps for years. Every product is made for both platforms. iOS and Android are two arcs of the same ellipse, not a finished app and a leftover sketch.

Behavior is watched and written down before any screen is inked. Design then draws hierarchy, type, and the marks a person actually taps. The build gives each platform the navigation, density, and system controls that already belong to it. Testing walks those same tasks on both. Release puts both builds into the world, and later updates stay on that chart instead of drifting into a private fork.

The frames beside this text show the shared plan, not a costume pulled over one codebase. A fang mark is a step. A ring is the boundary of the product. If a feature is on the chart, it is built for both arcs, reviewed on both, and updated on both.

iOS9:41

Shared plan

  • Behavior
  • Design
  • Build
  • Testing
  • Release
‹ Android9:41

Same ring

  • Behavior
  • Design
  • Build
  • Testing
  • Updates

02 — Approach

Five strokes close the ring

The work is a sequence, and the sequence is the product. A picture of a screen is not a release. The ring closes only when both platforms have walked the same path.

  1. 01

    Behavior

    Sit with the task. Write the path a person takes, including the wrong turn, the pause, and the moment they need an answer. The chart starts here, before a screen exists, so later strokes have something true to follow.

  2. 02

    Design

    Ink the screens. Hierarchy, type, and tap targets are drawn so the path stays visible. The drawing is checked against the behavior notes, not against a mood. What does not help the task does not earn a mark.

  3. 03

    Build

    Make it for iOS and for Android from the one plan. Each platform keeps its own gestures and system type. The shared plan keeps the tasks, the assistant, and the privacy rules identical on both arcs.

  4. 04

    Testing

    Walk the path on both platforms. Fix what breaks the task, what misses a control, and what the assistant answers poorly. Testing is a stroke of the ring, not a glance the night before release.

  5. 05

    Release and updates

    Ship both builds. When a fix or a later change is ready, update both. The orbit does not end at the first release. The chart stays the record of what the product is allowed to do.

03 — Comparison

Twin frames

The platforms differ where the operating system differs. They do not differ in the plan, the assistant, or the privacy boundary. Read the two frames as one product seen from two sides.

iOSHome gesture

iPhone frame

  • System type
  • Familiar controls
  • Same tasks

iOS

  • Navigation follows iPhone patterns, including the home gesture at the bottom of the frame.
  • Type and controls are drawn for that frame, so the app does not feel like a visitor.
  • Testing happens on iOS before release, on the same tasks the Android build must pass.
  • Updates ship to the iOS build whenever the shared plan changes.
‹ AndroidSystem back

Android frame

  • System back
  • Local density
  • Same tasks

Android

  • Navigation follows Android patterns, including the system back control.
  • Type and density are drawn for that frame, not scaled down from the other arc.
  • Testing happens on Android before release, against the same written behavior.
  • Updates ship to the Android build on that same schedule of changes.

One shared plan. The in-app assistant, the unique id, Singular, and OneSignal follow the same rules on both platforms. Nothing in this comparison is a second product with a quieter promise.

04 — Manifesto

The closed ring

If it is not on the chart, it does not ship.

Names, inboxes, phone books, and precise places stay outside the ring. The only mark that identifies an install is a unique id. Two platforms still mean one boundary. KEPLER WOLF LIMITED would rather leave a blank on the chart than invent a profile to fill it.

05 — Capabilities

Marks along the path

These are the practices the studio actually keeps. The line moves. The list does not grow extra claims.

  • Behavior studies
  • Interface ink
  • iOS builds
  • Android builds
  • One shared plan
  • On-device testing
  • Store release
  • Later updates
  • Assistant replies
  • Singular attribution
  • OneSignal push
  • A unique id

06 — Assistant

A voice inside the ring

The in-app assistant can talk with the person using the app. It is not a human. It is not professional advice. What someone writes is used only to answer that person, and it is not passed to other users.

The apps build no personal profile. Users do not send personal data to each other. A conversation with the assistant is a reply, not a channel between people and not a dossier that follows anyone out of the session.

The panel is a picture of that kind of answer. It is not a live assistant on this website, and it cannot take a question from you here. The real assistant lives inside the app, under the same limits on both platforms.

Assistant

Not a person

Is this a person?

No. I am the in-app assistant. I am not a human, and this is not professional advice.

Do you pass this to other people?

No. What you write is used only to answer you. It is not passed to other users.

Do you keep a profile of me?

No. The app builds no personal profile. The only identifying item is a unique id, used for Singular attribution and OneSignal push.

07 — Privacy

Off the chart

Attribution uses Singular. Push notifications use OneSignal. The only identifying item is a unique id. The apps do not collect a name, an email, a phone number, a contacts list, or a precise location in order to describe a person.

Singular

Attribution only. A unique id ties an install to a listing or a campaign. It does not introduce one user to another.

OneSignal

Push only. If you allow notifications, OneSignal delivers them to that device. A push is not a message from another user.

Unique id

The only identifying item. It serves attribution and push. It is not a name, a phone number, or a map pin.

No profile

No name, email, phone, contacts, or precise location is gathered to build a portrait of the person holding the phone.

No exchange

Users do not send personal data to each other. There is no shared inbox and no directory of people.

Mail, separately

Email to the developer is written in your own mail app. It is not mixed into the unique id or shared with other users.

Read the privacy note

08 — Contact

Write the observatory

The developer is KEPLER WOLF LIMITED. Write directly, or use the contacts page, which opens your mail app and does not store the note on this site.

[email protected]

Contact the studio Read the privacy note Read the terms