恋みくじ

I have been building a small web product around a concept that is immediately familiar to many people in Japan but difficult to explain in a single sentence to someone outside the country.

The product is based on 恋みくじ—Japanese love fortunes inspired by the omikuji traditionally found at shrines and temples.

In Japan, most people already understand the basic ritual. You think about something important, draw one fortune, read the message, and consider how it relates to your current situation.

The product does not need a long onboarding process because the culture has already taught users how to use it.

But what happens when the same product is introduced to people who have never encountered an omikuji?

That is the question I am currently trying to answer.

A product that grew through cultural familiarity

I launched the Japanese version in 2023.

The experience is deliberately simple. A visitor thinks about their current romantic situation, draws one 恋みくじ, and receives a short message for the day.

There is no registration, no email address, and no personal information required.

The product currently includes a daily love fortune and a situation-based version for concerns such as unrequited love, reconciliation, unanswered messages, and long-distance relationships.

Together, the two versions have generated more than 4.9 million draws.

The existing product is [Ichizendo Koi Mikuji] 一禅堂.

Its growth has made me consider an English version. However, the more I think about localization, the less it feels like a translation project.

It feels like a product-design problem.

The words can be translated, but can the ritual?

The most obvious option would be to translate 恋みくじ as “love fortune.”

That translation is understandable, but it loses some of the original context.

For a Japanese user, “omikuji” is not simply a random prediction. It is connected to a familiar ritual: visiting a shrine, drawing a numbered stick or paper, unfolding the result, and reflecting on what it may mean.

Some people take the result seriously. Others enjoy it casually. Many do both at the same time.

That balance is important.

The experience can feel meaningful without requiring the user to believe that every sentence is a literal prediction of the future.

When the product is described only as a “love fortune generator,” an English-speaking visitor may imagine something very different:

* A novelty random-text tool

* An astrology or horoscope website

* A dating compatibility quiz

* An AI relationship adviser

* A game with random romantic predictions

None of those descriptions is completely wrong, but none captures the original experience either.

The interface can be translated in a few hours. The cultural expectation behind the interface cannot.

Should the Japanese name be preserved?

One possibility is to keep the name “Koi Mikuji.”

This preserves the identity of the product and gives users an opportunity to discover something specifically Japanese.

However, an unfamiliar name creates friction.

Someone seeing “Koi Mikuji” for the first time may not know:

* What the product does

* Whether it is a game or a serious service

* What “koi” means

* What “mikuji” means

* Why they should draw only once per day

A descriptive subtitle could solve part of this problem:

> Koi Mikuji — A Japanese Love Fortune for Daily Reflection

This approach keeps the original cultural name while immediately explaining the function.

The alternative would be to remove the Japanese term and use a fully localized name such as “Daily Love Fortune.”

That would be easier to understand, but it would also make the product look similar to many generic fortune and horoscope websites.

The Japanese context is not decoration added to the product. It is the reason the product exists.

Removing it may improve immediate comprehension while weakening the product’s identity.

Literal translation can change the emotional tone

The messages inside a 恋みくじ are short. That makes their tone especially important.

A long article has space to explain itself. A short fortune may have only one or two sentences.

In Japanese, a message can feel gentle, indirect, and emotionally open. A literal English translation may sound vague, awkward, overly dramatic, or even cold.

For example, a Japanese message may suggest waiting without directly commanding the reader to wait. It may imply that someone should reconsider a relationship without explicitly saying, “You should leave.”

This indirectness gives the user room to connect the message to their own situation.

English product copy often values clarity and directness. But if every message becomes too direct, the experience may start to feel like advice rather than reflection.

There is also a question of emotional responsibility.

People often open a love fortune when they are already uncertain. They may be waiting for a reply, thinking about an ex, or wondering whether someone shares their feelings.

A message should not promise that a person will return, guarantee that a relationship will succeed, or make an important decision on the user’s behalf.

The Japanese product presents each result as a prompt for self-reflection rather than a fixed prediction.

That principle needs to survive localization, even if the wording changes completely.

Three possible approaches

I currently see three ways to bring the product to an international audience.

1. Translate the existing product directly

This is the fastest approach.

The interface, explanations, and existing fortune messages would be translated into English. The product structure would remain almost identical to the Japanese version.

Advantages:

* Faster to launch

* Lower development cost

* Easier to maintain

* Preserves the existing product experience

Risks:

* Messages may feel translated rather than naturally written

* Cultural meaning may be lost

* The product may require more explanation than expected

* Japanese romantic situations may not map perfectly to other cultures

This approach would test whether the core interaction works globally, but a weak translation could produce a false negative. Users might reject the wording rather than the concept.

2. Rebuild the experience for English-speaking users

Instead of translating existing fortunes, I could treat the English version as a related but separate product.

The core ritual would remain: think about a romantic concern, draw once, and reflect on the result.

However, the messages, categories, examples, and explanations would be written specifically for English-speaking users.

Advantages:

* More natural language

* Better cultural fit

* Greater freedom to test new categories

* A clearer experience for first-time users

Risks:

* More expensive and time-consuming

* Harder to maintain two content systems

* Greater chance of losing the original Japanese identity

* The result may become a generic relationship-advice product

This could create a better localized product, but it raises a difficult question: at what point does adaptation become a different product?

3. Keep the Japanese ritual and teach users how to experience it

The third approach is to preserve 恋みくじ as a Japanese cultural experience.

Instead of hiding the unfamiliar parts, the product would explain them.

A short introduction could tell users:

* What omikuji is

* What “koi” means

* Why the product recommends one draw per day

* Why the result is not a guaranteed prediction

* How to reflect on the message

* How the online version relates to the traditional ritual

Advantages:

* Stronger differentiation

* Preserves the product’s origin

* Gives users a reason to remember and share it

* Creates a cultural experience rather than another generic fortune tool

Risks:

* More onboarding friction

* Some users may leave before drawing

* Cultural explanations can become too long

* The experience could feel educational rather than emotional

This is the approach I find most interesting, but it requires careful design. The explanation must provide context without standing between the user and the main action.

What should remain universal?

Although the product is culturally specific, the emotional situations behind it are not.

People everywhere experience uncertainty in relationships.

They wait for replies. They wonder whether to confess their feelings. They think about reconnecting with someone. They struggle with distance, timing, and unspoken expectations.

The language and customs may change, but the underlying emotions are recognizable.

This may be the bridge between the Japanese product and a global version.

Instead of translating every cultural detail, the product could preserve the ritual while rewriting the messages around universal emotional moments.

The experience would remain Japanese in origin but would not require users to behave or communicate exactly like Japanese users.

How I am thinking about testing it

Rather than translating the entire product immediately, I am considering a smaller experiment.

The first version could include:

* A short English landing page explaining Koi Mikuji

* A limited collection of messages written directly in English

* Three or four universal relationship situations

* No registration or personal-data requirements

* One draw per day

* A simple way to save and share the result

* A short feedback question after the experience

The first goal would not be revenue.

It would be to understand whether users outside Japan find the ritual meaningful, confusing, entertaining, or emotionally useful.

I would want to learn:

* Do users understand the product before drawing?

* Does the Japanese name create interest or confusion?

* Do they interpret the result as reflection, entertainment, or prediction?

* Does the once-per-day recommendation make the experience feel meaningful or unnecessarily limited?

* Which relationship situations feel universal?

* How much cultural explanation is useful?

* Would users return without notifications?

These answers would help determine whether the product needs translation, adaptation, or a completely different global experience.

The risk of making a cultural product too universal

There is a common temptation in localization: remove everything unfamiliar so that the product becomes easy for everyone to understand.

But unfamiliarity can also be valuable.

People travel, read, watch films, and try new products partly because they want to experience something outside their own culture.

If every Japanese element is replaced with a familiar Western equivalent, the product may become easier to understand but less interesting.

The goal may not be to make Koi Mikuji feel as if it originated everywhere.

The goal may be to make its Japanese origin understandable and welcoming to people everywhere.

That is a different design objective.

I would like to hear how other founders approach this

Many Indie Hackers build products for global audiences from the beginning. Others start with a local market and expand only after finding product-market fit.

Cultural products create an additional challenge because localization affects more than menus, currencies, and date formats. It can change the meaning of the product itself.

I would appreciate the community’s perspective:

1. Would you keep the name “Koi Mikuji,” or replace it with a descriptive English name?

2. Would you translate the existing messages or write a completely new English collection?

3. How much cultural explanation would you include before the user’s first interaction?

4. Is the Japanese origin the product’s strongest advantage, or a barrier to global adoption?

5. Have you ever localized a product built around a tradition, habit, or emotional behavior specific to one country?

6. How did you decide which parts to preserve and which parts to redesign?

I am especially interested in examples where a culturally specific product succeeded internationally without becoming a generic version of itself.

Can a product built for one country work globally?

I believe it can—but only if localization protects the reason people cared about the original product in the first place.

I Built a Japanese Fortune Web App That Generated 4.9 Million Draws

In 2023, I launched a small web product based on a familiar part of Japanese culture: 恋みくじ, or “love fortune.”

The idea was simple. A visitor thinks about their current romantic situation, draws one fortune, and receives a short message for the day.

There is no account to create, no email address to submit, and no personal information to enter. The product is free and can be used directly in a browser.

At the time of writing, its two versions have generated more than 4.9 million draws.

The product is called Ichizendo Koi Mikuji.

It is not a technically complicated SaaS product, and it does not solve a traditional business problem. However, building it has taught me a great deal about cultural products, search intent, repeat usage, emotional design, and why a narrow idea can sometimes grow more effectively than a broad one.

What is Koi Mikuji?

In Japan, an omikuji is a paper fortune traditionally drawn at a shrine or temple. People often draw one at the beginning of the year, while traveling, or when they want guidance about an important part of life.

恋みくじ focuses specifically on love and relationships.

A typical 恋みくじ may contain a short message about meeting someone, expressing feelings, waiting patiently, reconsidering a relationship, or having the courage to move forward.

I wanted to bring a small part of that experience online without making it feel like a complicated personality test.

The current product has two main versions.

The first is a daily version. It gives users a simple message about their love life and is designed to be drawn once a day.

The second is situation-based. It lets users choose a concern such as unrequited love, reconciliation, waiting for a reply, or a long-distance relationship before drawing a more relevant message.

The result is not presented as a guaranteed prediction. It is intended to be a small prompt for reflection—a way to pause, recognize what someone is feeling, and think about what they may want to do next.

Why the idea works in Japan

One important lesson from this project is that a product does not always need to teach users a completely new behavior.

Japanese users already understand the basic idea of omikuji. The concept carries cultural meaning, and many people know what to expect before opening the page.

That familiarity reduces the amount of explanation the product needs.

The user does not have to learn a new system, complete a long onboarding process, or understand a technical feature. They only need to think about their current situation and draw a fortune.

At the same time, moving 恋みくじ online changes the context in useful ways.

A physical omikuji is usually connected to a visit to a shrine or temple. An online love fortune is available when someone is alone at night, waiting for a message, thinking about a person, or feeling unsure about a relationship.

That moment matters.

People rarely search for relationship guidance when everything feels clear. They search when they are uncertain. A product that can respond immediately to that emotional moment has a natural reason to exist.

This taught me that cultural familiarity and digital convenience can be a strong combination. The underlying idea may be old, but the context in which people use it can be completely new.

Why I built a web app instead of a native app

I chose the web because I wanted the first interaction to be almost effortless.

Installing an app is a significant commitment for something a person may initially use out of curiosity. A web experience removes that barrier.

A visitor can open the page, draw a 恋みくじ, save the result, and leave without creating an account.

The web also makes sharing easier. Someone can send the URL to a friend or share a saved result through social media without asking the other person to install anything.

This approach has limitations. Native apps can provide notifications, stronger retention mechanics, and a more controlled interface. But for this product, accessibility was more important than building an aggressive retention system.

The product should feel like a place people choose to visit, not something constantly asking them to return.

Another advantage of the web is search discovery. Each supporting article can explain a different part of the experience: what 恋みくじ means, how online omikuji differs from shrine omikuji, how to interpret a result, and why certain messages feel emotionally relevant.

The main product offers a short experience, while the surrounding content gives search engines and new visitors enough context to understand it.

Search intent mattered more than technical complexity

The core product is technically straightforward. Its growth did not come from using the most advanced technology.

It came from understanding a specific intent.

People searching for 恋みくじ are usually not looking for a long academic explanation. They want to draw a fortune.

This means the product page needs to answer the user’s main intention quickly. The action should be visible, the page should work well on mobile devices, and unnecessary steps should be removed.

However, a page that contains only a button and a random result provides very little context. It may be convenient for existing users, but it is harder for new visitors—and search engines—to understand.

Over time, I added clearer explanations around the experience:

• What a love fortune is

• How to draw one

• Why the service recommends one draw per day

• How users can interpret a message

• The difference between the daily and situation-based versions

• Privacy information

• Answers to common questions

• Related articles about the history and meaning of omikuji

The goal was not to fill the page with keywords. The goal was to answer the questions a first-time visitor might naturally have.

This balance is important. The action should remain simple, but the page should also provide enough trust and context to stand on its own.

Why I recommend only one draw per day

Many digital products try to maximize the number of actions a user performs.

For a fortune product, it would be easy to let people draw repeatedly until they receive the answer they want. That might increase short-term engagement, but it would weaken the meaning of each result.

Ichizendo recommends drawing one official 恋みくじ per day.

This is not a technical restriction designed to create artificial scarcity. It is a product principle.

If users can immediately replace an uncomfortable message, the result becomes disposable. When they are encouraged to keep one message for the day, they are more likely to think about why it affected them.

Sometimes a message feels encouraging. Sometimes it feels uncomfortably accurate. Sometimes it does not seem relevant until later.

The small amount of friction gives the experience weight.

This decision also helped me think differently about engagement. More clicks are not always the same as more value. In some products, the right limit can make an interaction more meaningful.

What I learned from 4.9 million draws

The largest lesson is that emotional relevance often matters more than feature quantity.

Users do not return because the product has dozens of settings. They return because they are still thinking about a person or a relationship.

The same user may interpret the same sentence differently depending on what happened that day. The value is created partly by the words and partly by the user’s current emotional context.

I also learned that short content is difficult to create well.

A long article has room for explanation and nuance. A short fortune may have only one or two sentences. Every word affects the tone.

If the message is too vague, it feels meaningless. If it is too specific, it may not apply to enough people. If it is too positive, it feels dishonest. If it is unnecessarily harsh, it can make someone feel worse without offering any useful perspective.

The most effective messages usually do three things:

1. Recognize a feeling or situation.

2. Offer a different perspective.

3. Suggest a small, realistic next step.

Another lesson was the importance of privacy.

Relationship concerns can be deeply personal. Requiring a name, email address, birthday, or detailed personal story would create unnecessary hesitation.

The product therefore works without registration or identity information. A visitor can use it privately and leave.

That simplicity is not an absence of features. It is part of the product’s value.

Sharing became part of the experience

Some users want to keep a result because a particular sentence feels meaningful. Others want to send it to a friend or post it on social media.

For that reason, results can be saved as images and shared.

This creates a natural distribution loop, but it is different from a conventional referral program. Users are not sharing because they receive credits or unlock a feature. They share because the message expresses something they were already feeling.

That distinction matters.

The best sharing mechanism is often not a “Share this product” button. It is an output that people genuinely want to show someone else.

For Ichizendo, the result itself became that output.

How the product makes money

The service is currently free and primarily supported by advertising.

This model keeps the main experience accessible, but it requires care. Advertising can easily interrupt an emotionally focused product, especially on a mobile screen.

The challenge is not simply adding more ad placements. It is finding a balance between sustainability and trust.

If advertisements make the page feel crowded or prevent users from reaching the main action quickly, short-term revenue can damage long-term usage.

I am also considering additional paid experiences in the future, but I do not want to place the basic daily 恋みくじ behind a paywall.

The free experience is the foundation of the product. Any paid feature should add genuine depth or convenience rather than remove something users already have.

What I plan to build next

The current experience was designed primarily for Japanese users. One of the biggest questions now is whether the concept can work for people who did not grow up with omikuji culture.

A direct translation may not be enough.

Japanese users already understand the emotional and cultural context of drawing a fortune. English-speaking users may need a clearer explanation of what Koi Mikuji is, how it should be interpreted, and why drawing only once per day matters.

This makes localization a product-design challenge, not just a language task.

I am also exploring ways to improve the situation-based version, make saved results more personal, and allow users to contribute their own carefully reviewed messages.

At the same time, I want to preserve the simplicity that helped the original product grow.

Every new feature creates a risk: the product can become more capable but less understandable.

The biggest lesson

Before building this product, it would have been easy to dismiss the idea as too small, too local, or not technical enough.

But narrow products have an important advantage: they can be specific.

Ichizendo Koi Mikuji does not try to solve every relationship problem. It offers one simple experience for one recognizable emotional moment.

That clarity helped people understand it, search for it, use it without instructions, and share it with others.

More than 4.9 million draws later, I am still learning how far a culturally specific product can travel without losing what made it meaningful in the first place.

I would be interested to hear from other Indie Hackers:

• Have you built a product around a local cultural behavior?

• How did you explain it to users in other countries?

• Would you translate a product like this directly, or redesign the experience for a global audience?