Consumer platform / Custom application

Numa

Keep personal context connected across the product.

Astrology, tarot, conversations and journaling brought into one connected account. A calm interface makes a complex content platform feel approachable.

Puzinski’s contribution

Consumer application development and integration across profiles, chart calculations, saved readings, conversations and journaling.

Explore the product

Daily feed

Numa — Daily feedInspect at full size ↗

Numa / Daily feed / Desktop

The business problem

Give returning users a clear way to find personal content and continue where they left off.

When every feature behaves like a separate tool, personal context gets lost and useful past content becomes difficult to find.

The product decision

Keep the daily starting point concise, then give chart exploration, reading history and journaling dedicated views. Shared account data connects them.

A useful fit for
Consumer platforms, content memberships, personalized experiences and account-based mobile products.

Implemented scope

The work
it brings together.

A connected consumer experience: personal context, calculated data, saved content and new reflections belong to the same account.

  • 01Account and relationship profiles
  • 02Calculated chart views
  • 03Saved readings and conversations
  • 04Personal journal and validation
  • 05Responsive product navigation
  1. Open the daily feed
  2. Explore a calculated chart
  3. Revisit a saved conversation
  4. Save a personal reflection
The phone experience

A clear decision.
At each step.

Use a shared account model, a focused daily feed and direct access to reading history instead of separate content silos.

Numa — Return to saved content

Return to saved content

The reading library keeps previous content available as part of the account history.

Numa — Continue the conversation

Continue the conversation

Saved conversations remain connected to the account and can be revisited alongside other content.

Numa — Write and save

Write and save

Journal entries use server-side length validation and duplicate-save protection in the application.

Try the workflow

Explore Numa.

Enable JavaScript to try the browser walkthrough. The screens, scope and product decisions are available above.

Interactive walkthrough · changes stay on this device. Use sample details. “Reset walkthrough” clears this example’s progress.

The structure behind the interface

Connected by
design.

Personal content needs continuity. A reading is more useful when the person can recover it and keep a reflection alongside it.

01

Experience

Daily feed, charts, content history, relationships and journal.

02

Application

Profiles, calculated data, reading jobs, AI integration and usage entitlements in the application codebase.

03

Persistence & delivery

PostgreSQL and Prisma account models, Next.js interfaces and native integration source.

Observed acceptance checks

Open the connected account
Chart, reading and journal models load together.
Retry the same journal save
The retry retains one entry rather than adding a duplicate.
Submit a blank or very short entry
The server rejects the invalid entry.
Product decisions & tools
A useful starting point
The home screen pairs a concise daily reading with relevant context, recent content and direct routes into the rest of the product.
One connected account
Profiles, birth data, saved readings and journal entries share the same underlying account rather than separate screen-level data.
Mobile navigation with priorities
Four primary destinations stay available on phones. Detailed chart, reading and journal views use the remaining space for content.
Implementation
Next.js · React · TypeScript · PostgreSQL · Prisma
A product built around your business

Let’s shape
your first release.

Tell us the users, the key tasks, the existing tools and what a useful first version needs to do. We’ll clarify the scope, data, review points and delivery requirements.

Numa / Product screen