Why it was needed
01A fortune product stalls when it ends at one result screen. Catalog entry, input, results, payments, collection, and history had to continue naturally.
AI fortune web product
A consumer web product that combines AI readings, crystal checkout, Kedi collection, and counselor chat in one app-like flow.

Fortune / AI
AI fortune web product that connects readings, crystals, Kedi collection, and counselor chat.
Project overview
Kedigram is a consumer web product built around AI fortune experiences such as coffee readings, tarot, dream interpretation, compatibility, and daily horoscope. The product does not stop at a single reading result; it connects catalog entry, result screens, crystal purchases, Kedi collection, and counselor chat inside one app-like surface.
The implemented scope shows a Next.js product with home, content, result, shop, kedigram, chat, and history routes, plus next-intl localization, Orval-generated API clients, React Query state sync, Google OAuth login, wallet and payment checkout, gacha reveal interactions, and OG/SEO rendering. It behaves much closer to a repeat-use consumer service than a simple landing page.
Why it was needed
01A fortune product stalls when it ends at one result screen. Catalog entry, input, results, payments, collection, and history had to continue naturally.
What I built first
02I split the product into home, content, result, shop, kedigram, chat, and history flows in Next.js, then tied API state, localization, and OG rendering into one product.
Where this approach works well
03This fits consumer web products that need content consumption, light payments, collection mechanics, and repeat-use loops together.
Technical details
Web frontend
State and API layer
Product loops
Product surfaces
The screens below are the actual interfaces that defined the product experience.



Contact
A short brief, a reference link, or the current problem definition is enough. I can help structure the right first version from there.