Taibu 缺少地理編碼備援,揭示中國占星產品的 UX 問題
What a Missing Geocoding Fallback Taught Me About Chinese Astrology UX
Taibu 的地理編碼服務未有設定,令出生地資料未能用於真太陽時校正,暴露出介面收集輸入卻沒有使用的 UX 問題。測試指出,產品應停用出生地欄位並解釋原因、提交前驗證位置並顯示經度,或顯示真太陽時及時差。文章亦肯定其紫微鬥數宮位互動和基本資訊頁。
I tested a Chinese astrology product called Taibu with a synthetic birth record: 1992-09-18 14:30, Shanghai, male. The goal was not to compare interpretations. It was to see how the product handles inputs, chart output, and the boundary cases that every astrology calculator eventually hits.
This is an AI-assisted draft, reviewed and edited by me. The test was run on 2026-11-15.
The happy path is fast
The BaZi page does not require login. The form asks for an optional name, gender, calendar type, birth date/time, and an optional birthplace. The default date is today, so a first-time user has to replace it.
After submit, the result page opens with a “professional chart” view: four pillars, ten gods, hidden stems, growth phases, void branches, na-yin, and shen-sha, followed by decade luck, annual luck, and monthly luck.
That is a lot of information, but it is the right information for someone who already knows BaZi. The issue is the default.
A second view does most of the onboarding
The product also has a “basic information” tab. It starts with the day master and then explains the ten gods in plain language, marking which ones appear in the chart.
That tab is a much better first screen for a new user. The professional table is still there, but it no longer has to carry the onboarding burden.
The lesson: if a chart has two audiences, give them two entry points. Do not make the expert view explain itself to beginners.
The Ziwei chart has the best interaction
The Ziwei result starts with the key facts: five-element bureau, life palace, body palace, and current decade. Below that is a twelve-palace grid with natal, period, and flying-star tabs.
Clicking a palace updates the triangle and opposite palace, and the side panel shows the main stars, auxiliary stars, minor stars, and decade range for that palace.
This is the strongest part of the product. A static twelve-palace table is hard to read; a palace-level detail panel gives the user a path through the chart.
The boundary case is where it breaks
I selected Shanghai / Huangpu. The result page still showed:
Geocoding service is not configured; true solar time will not be used this time.
The birthplace field exists, but it did not affect true solar time in this run. The chart happened to stay the same because the clock time remained inside the same two-hour branch, but the user has no way to know that from the UI.
This is not a chart-calculation bug. It is a product contract bug: the interface collects a value and then silently does not use it.
If the geocoding service is unavailable, the product should do one of three things:
- Disable the birthplace field and explain why.
- Validate the location before submit and show the longitude that will be used.
- Show the computed true solar time next to the clock time, including the offset.
Silently falling back is the worst option because it teaches the user to trust a correction that did not happen.
What I would keep
- No login for the first chart.
- A basic view and a professional view.
- Palace-level interaction for Ziwei.
- Save, share, copy, and ask-follow-up actions on the result page.
What I would change
- Put a short conclusion block above the professional table.
- Make the birthplace field prove that it was used.
- Keep the basic explanation visible before asking the user to save.
- Treat “unknown” as a first-class state, not an error message at the bottom of the page.
Cross-check note
I ran the same synthetic sample through the Liki astrology engine and compared the four pillars and key Ziwei fields. They matched on this sample. That is one sample, not a claim about overall accuracy.
The product is capable. The next step is not more features; it is making the existing inputs and outputs honest about what happened.
Boundary: traditional culture perspective, for reference only, not professional advice. 传统文化视角,仅供参考,不构成专业建议。
Disclosure: I work on Liki. Taibu is an independent product and we have no partnership. This is a product UX test, not a fortune-telling recommendation.
來源:DEV Community · dev.to