Back to site
Horoscope App

Minimal app page

A horoscope reader shaped around the daily ritual, not the scroll.

This repo packages a calm horoscope surface: choose a sign, pick a focus, move between daily, weekly, and monthly views, and keep the reading available even when live APIs are not.

  • 12 signs
  • 3 reading ranges
  • 10 visual themes
  • Web plus iOS and Android shells
Illustrated poster for Horoscope App with crescent moon motif and reading controls

A small reading surface with enough structure to become a habit.

The repo describes a static horoscope app with a ritual-first UI. The current product surface is built around short readings, quick sign switching, mood-led themes, and installable packaging through Capacitor.

It is not framed as a finished app-store launch. The public-safe read is tighter: a packaged prototype with a credible reading loop, an offline fallback, and a clear path from web build to phone install.

The product is strongest where the repo is most concrete.

Three reading ranges

Daily, weekly, and monthly tabs are built into the interface, so the product can hold both quick ritual use and slightly longer sessions.

Focus-aware reading

The UI already separates general, love, career, money, and health. That keeps the reading surface lightweight while still feeling personal.

Theme packs, not just dark mode

Ten named palettes are present in the app shell. The product identity is clearly about mood and atmosphere, not just text blocks on a blank screen.

Flexible content paths

The repo supports a secure server-side proxy, direct API entry, a public demo endpoint, placeholder copy, and a local generator for offline use.

Ritual extras

Favorites, lucky color and number, compatibility, archive toggles, and energy bars are already represented in the current interface.

Native-ready packaging

Capacitor shells for iOS and Android sit beside the web build, which means the same product world can move from browser preview to device install.

Three ways this repo already knows how to behave.

  1. 01

    Daily check-in

    Save one sign, keep the reading short, and use the one-line lead as the first thing you see before the longer text.

  2. 02

    Offline or low-friction fallback

    When no provider is available, the local generator and placeholder copy keep the app useful instead of collapsing into an empty shell.

  3. 03

    Phone install path

    The web surface can be synced into iOS and Android shells, which makes this repo suitable for personal builds and private testing on actual devices.

No screenshots are stored in the repo, so this export uses illustrated product artifacts instead.

Illustrated reading board showing horoscope card, focus controls, and energy bars
Illustrated board based on the current sign picker, reading card, and energy layout.
Illustrated poster using the crescent moon icon system from the repo
The export uses the existing moon-and-stars icon system as the main public preview image.

What the repo supports today, without overstating anything.

Signs 12

Every zodiac sign is represented in the current selector and local generator.

Reading ranges 3

Daily, weekly, and monthly views are present in the app surface.

Theme palettes 10

Named palettes in the repo support a stronger visual mood than a single skin.

Content modes 5

Secure proxy, direct API key, public demo, placeholder copy, and local generation.

Platforms in repo 3

Web build, iOS shell, and Android shell are all present in the current tree.

Publication status Private build

No evidence in the repo suggests an app-store release or live production deployment yet.

The app is presented as entertainment. The repo also shows a secure proxy option for keeping provider keys off the client when live API use becomes necessary.

The current public-safe answers.

Is this already published to an app store?

No app-store listing or store metadata is evidenced in the repo. The current state is best described as a packaged prototype with native shells.

Does it need an API to work?

No. The repo includes placeholder copy and a local generator, so the reading flow can still function without a live provider.

What is the secure proxy for?

It moves provider keys to the server side. That matters once the app stops being a personal test and starts needing private API credentials.

What makes the interface distinct?

The existing product leans into the ritual: sign selection, focus selection, palette changes, a one-line lead, and visible energy bars rather than endless text.

A clear product world already exists here. The next step is distribution, not reinvention.

This export keeps the claim set tight: an installable horoscope reader with a defined mood, observable feature set, and a credible path from browser build to phone test.