← All writing
Projects · Open web · Product

Introducing iWebTools: three focused products, one way of building

Meet SimpleCalc, JSONDock, and EncodeLab—and the product principles connecting our calculators, JSON workspace, and encoding tools.

There is no shortage of online tools. Search for a mortgage calculator, a JSON formatter, or a Base64 decoder and you will find pages of results.

The problem is rarely that a tool does not exist. The problem is that many tools ask for too much attention before they provide an answer. They surround a small task with advertising, hide the useful interface below generic content, work poorly on a phone, or send input to a server when the browser could have handled it locally.

iWebTools is our attempt to take a different path: build focused products that open quickly, explain themselves clearly, and respect the work users bring to them.

Today, the family includes three live projects.

SimpleCalc: practical calculators with explanations

SimpleCalc is our calculator collection for financial, mathematical, and everyday decisions.

It currently includes 33 calculators across three categories:

A calculator can produce a number in a few lines of code. Producing a result that someone can understand and use responsibly is a larger product problem.

That is why SimpleCalc pages do more than display an input form. They state assumptions, validate impossible values, explain the result, answer common questions, and link to related tools. The Rent vs. Buy Calculator, for example, includes transaction costs, insurance, opportunity cost, and a year-by-year break-even view rather than reducing the decision to one monthly payment.

Every calculation runs in the browser. There is no account, database, or server receiving the values entered into a form.

Explore SimpleCalc →

JSONDock: a calm workspace for difficult JSON

JSONDock is a browser-based workspace for formatting, validating, repairing, searching, and exploring JSON.

The familiar JSON formatter is only the starting point. Real documents arrive truncated, double-escaped, deeply nested, or filled with numbers that cannot safely pass through the standard JavaScript Number type. JSONDock is built for those less tidy situations.

It combines:

This matters because a developer tool should not quietly change the data it is supposed to inspect. Many simple formatters parse a document into ordinary JavaScript numbers and serialize it again. That can round a large identifier or alter a high-precision decimal without making the change obvious. JSONDock preserves original number tokens so formatting does not become accidental data corruption.

The entire workflow stays in the browser. There is no upload step, user account, analytics pipeline, or remote document storage.

Open JSONDock →

EncodeLab: deterministic conversion without the clutter

EncodeLab is our collection of encoding, cipher, and text-conversion tools.

Its first 12 pages cover binary translation, text and binary conversion, Morse code, hexadecimal, ASCII and Unicode code points, Base64, Caesar ciphers, and general cipher decoding.

Each page is a real standalone tool—not a keyword page with a small converter buried under marketing copy. The converter is the primary content, with validation, examples, explanation, FAQs, and related tools supporting the task.

Conversions are deterministic and local. UTF-8 text uses browser-native byte encoders and strict decoding. Binary input is validated as complete bytes. Large binary numbers use BigInt instead of floating-point values. Base64 is described accurately as encoding, not encryption, and classical ciphers are not presented as modern security.

That combination of implementation detail and honest explanation is central to the product. A converter should not merely return output; it should help users understand what format they are working with and when it is appropriate.

Explore EncodeLab →

What connects the projects

The three products look and behave differently because their tasks are different. A mortgage calculator should not feel like a code editor, and a JSON workspace should not be squeezed into the same interface as a text converter.

They do share a set of defaults.

Local processing whenever practical

Calculations, JSON transformation, and text conversion happen on the user’s device. This reduces latency and gives the products a privacy model that is easier to explain: the input does not need to leave the browser to produce the result.

No account before value

None of the current products requires registration. There is no dashboard to configure and no workspace to organize before the primary tool becomes available.

Static pages for durable discovery

The sites are built as independently deployable static applications. Important routes contain complete HTML, canonical metadata, structured data, sitemaps, and explanatory content. This makes the products fast to deliver and understandable to both people and search engines.

Clear limitations

Financial estimates include assumptions. Repair output must be reviewed. Base64 is not encryption. A trustworthy tool needs to communicate where its result ends and the user’s judgment begins.

Independent products, shared standards

Each product has its own domain, interface, release process, and roadmap. Shared standards—privacy, accessibility, responsive design, tested core logic, and useful content—provide consistency without forcing every task into one application.

What we are building next

The immediate goal is not to add dozens of unrelated tools as quickly as possible. It is to deepen useful areas and reuse proven foundations.

For SimpleCalc, that means expanding high-demand non-health categories, with scientific calculation, debt payoff, and additional unit converters among the next candidates.

For JSONDock, it means continuing to improve the document workflow while protecting the properties that distinguish it: lossless numbers, deterministic repair, powerful editing, and bilingual access.

For EncodeLab, it means adding adjacent conversions such as binary-to-decimal, decimal-to-hex, text-to-ASCII, ROT13, Vigenère, and Atbash while keeping every route genuinely useful. A composable conversion workbench may come later, but it will not replace focused, searchable tool pages.

The main iWebTools site will serve as the map and the workshop journal: a place to find every project, understand why it exists, and follow the decisions behind it.

We are still early. But the direction is established: smaller products, clearer outcomes, and tools that respect the user’s flow.