This page records meaningful changes across the inblooms family. It focuses on user-facing decisions, privacy and reliability work, and the checks performed after a release rather than listing every small code edit.
Content, translations and trust information
Expanded guides and FAQs across the hub and newer tools, then completed Korean, Japanese, Chinese, Spanish, French and German versions so the detailed help is not English-only. Added standalone About and Contact pages, corrected privacy wording to distinguish local tool inputs from analytics and advertising, and published these build notes.
Checked: all seven language switches, internal links, metadata, structured data, sitemap entries, desktop and mobile layouts, and live HTTP responses.
DevBloom and EmojiBloom
Released a developer toolkit for JSON, YAML, text comparison, Base64, URL encoding, JWT inspection and SHA hashes, plus an emoji, kaomoji and special-character picker. Both keep working data in the browser and provide seven interface languages.
InvoiceBloom creates invoices, quotes, statements and receipts from a live document preview before exporting a PDF, preserving Korean and other scripts without a server. TimeBloom uses timestamp-based timing so countdowns, the stopwatch and Pomodoro sessions remain accurate when a tab is in the background.
Checked: totals and tax calculations, Korean PDF output, saved form state, timer transitions, background elapsed time, alarms and the main mobile workflows.
Core tool family improvements
Added real-life calculators, random selection modes, cryptographic password generation, local photo metadata removal and color accessibility tools. PromptBloom gained shareable URLs, local history and output formats. Shared navigation, language behavior, favicons, structured data and font metrics were aligned across the family.
Checked: known calculation examples, cryptographic randomness usage, local file processing, URL state restoration, accessibility contrast calculations, layout shift risks and cross-site links.
How to read these notes
These are release summaries, not a claim that every browser, file or edge case is solved. A check describes what was exercised for that release. Reproducible problems and correction requests can be sent through the contact page and are used to guide later fixes.