Hoppscotch is an open-source Postman alternative (79,000+ GitHub stars) with Cloud, On-Prem, and Enterprise tiers. Someone started translating it into Japanese — 45% of strings are done. The problem is that a half-translated product often reads worse than an English-only one: it signals the effort stalled. Below is what that incomplete investment costs in the Japanese market, verified against the live repo and site.
The Japanese locale file (ja.json) contains 944 translated strings. The English source (en.json) has 2,078 strings. That is 45% coverage — meaning more than half the UI still renders in English when a user switches to Japanese. The file sizes confirm this: ja.json is 54 KB vs en.json at 109 KB.
github.com/hoppscotch/hoppscotch — locales/ja.json (54 KB, 944 strings) github.com/hoppscotch/hoppscotch — locales/en.json (109 KB, 2,078 strings)A Japanese developer switches to Japanese in settings and finds half the UI still in English — specifically the critical paths: some panel labels translated, others not. This pattern reads as "someone started and gave up." For a team evaluating API tooling for daily use, a product that appears to have abandoned its JP localization effort is a harder sell than one that was never attempted. Incomplete suggests instability.
Complete the remaining 1,134 strings and run a native-speaker pass for register (not just machine translation accuracy). The source strings already exist; this is an execution gap, not an architectural one. Once complete, JP should be visible in the language selector with a clear "Supported" state.
The hoppscotch.io Privacy Policy page exists and contains standard English-language terms. No 特商法に基づく表記 is present anywhere on the site or in the footer.
hoppscotch.io/privacy (footer links checked — no 特商法)Hoppscotch has Enterprise and Teams paid tiers. When a Japanese company considers paying for Cloud or Enterprise, the person handling the contract will look for the 特商法 page before signing off. Its absence is a known signal in Japanese B2B evaluation that the vendor is not set up for Japan. The evaluation either stops or routes to procurement escalation — either way, the deal slows.
A single 特商法に基づく表記 page with: company name, representative, address, contact, pricing structure, payment timing, refund policy. Template available. One day to produce, link in footer.
hoppscotch.io is a fully English-only single-page application. No language toggle is present in the marketing layer. The partial Japanese product locale exists inside the app, but there is no Japanese-language entry point from the marketing site.
hoppscotch.io (lang="en", no language switcher)A Japanese developer finds Hoppscotch via search or a blog post. They arrive at an English marketing site, which is fine — but when they want to share the evaluation with their team lead who is less comfortable in English, there is nothing to hand over in Japanese. The product itself partially speaks Japanese, but the front door does not. The evaluation stays personal and does not scale to a team purchase.
A Japanese landing page (even one page) covering the core value proposition, pricing, and an enterprise contact. This creates a shareable reference point for non-English-reading stakeholders.
Hoppscotch Cloud and Enterprise pricing is listed in USD. No JPY display or currency selector is available anywhere in the pricing or checkout flow.
API tooling is typically expensed through a team or department budget in Japanese companies. A USD subscription creates monthly exchange rate variance on an expense report, which is unusual enough to prompt questions from accounting. JPY display is not about currency conversion — it is about the purchase fitting into standard Japanese procurement workflow without requiring explanation.
JPY pricing display (at minimum alongside USD). For Enterprise contracts, a JPY-denominated option removes the last procurement friction for Japanese corporate buyers.
With no Japanese marketing pages, Hoppscotch does not appear in Japanese-language searches for API tooling alternatives. Japanese developers looking for 「Postman 代替 OSS」 or 「API クライアント 無料」 will not encounter Hoppscotch through search.
Japan has a strong preference for tools with visible Japanese adoption evidence — community articles, JP documentation, Japanese-language product pages. Without any of these, Hoppscotch is absent from the JP developer tooling evaluation moment entirely. Competitors with even minimal JP content show up; Hoppscotch does not.
The existing partial Japanese locale, once complete, provides the foundation. A Japanese-language product page targeting the「Postman 代替」long-tail captures the evaluation traffic that currently flows past Hoppscotch.
Five signal dimensions, each 0–20. Verified against the live site and repo on 2026-06-20:
| 1. Japanese marketing funnel | 2 / 20 |
| 2. Legal / trust (特商法) | 0 / 20 |
| 3. JPY billing / payment | 2 / 20 |
| 4. JP search visibility | 2 / 20 |
| 5. Product locale / IME / UX | 15 / 20 |
Dimension 5 is scored above 0 because a partial locale exists (45% complete). A complete, reviewed Japanese locale would raise this to 18–20. IME issues are not documented for this product type (REST client). The penalty here is specifically the stalled-halfway state, which is trust-damaging rather than neutral.
This map is the free slice. The full Japan-readiness audit covers the same gaps end-to-end, with specific copy, the 特商法 fields filled in, a ranked impact list, and a concrete action plan — delivered as a paid audit.
Data verified 2026-06-20 against hoppscotch.io, hoppscotch.io/privacy, and github.com/hoppscotch/hoppscotch. If something here is wrong or you'd like this page removed: hello@glovrex.com.