DEV Community: ao wang

Why Browser-Native DevTools Are the Invisible Superpower

ao wang — Sun, 12 Jul 2026 06:40:26 +0000

The best developer tools disappear. You stop noticing them. They become as invisible as the air you breathe while coding.

This is not a metaphor. It is a design principle.

The Fragmented DevTool Reality

Most developers have a bookmarks folder that looks like this:

JSON Formatter
Timestamp Converter
Base64 Encoder
URL Decoder
CSS Minifier

Each tab switch costs context. Each tool has slightly different UI conventions, different copy-paste quirks, different error messages. The cognitive overhead of using four single-purpose tools often exceeds the actual task difficulty.

Consolidation as a Philosophy

Opennomos Json (opennomos.com/en/project/01KJ850Z7PNGXHXESBM68HE12Y) consolidates timestamp conversion, JSON formatting, and Base64 encoding into a single workspace. The overhead disappears.

This is the north star: make the tool so simple that the user only thinks about their actual task — never about the tool.

The Trend

We have seen the same pattern across the ecosystem:

Codespaces made local environments invisible
Vercel made deployment invisible
Replit made runtimes invisible

The next frontier is developer utilities. The more invisible they become, the faster we ship.

Part of the Nomos Build-in-Public series.

Invisible DevTools: Why the Best Tools Disappear

ao wang — Sat, 11 Jul 2026 12:24:20 +0000

The best developer tools share one quality: you forget you are using them.

Think about it. Your IDE fades into the background when you are in flow. Your terminal becomes muscle memory. These tools are invisible because they match your mental model so perfectly that there is zero friction between thought and action.

This is exactly what online developer utilities should aspire to.

The Problem with Fragmented DevTools

Most developers have a bookmarks folder full of single-purpose websites:

One for JSON formatting
One for timestamp conversion
One for Base64 encoding
One for URL decoding

Every switch between these tabs is a context loss. Every tool has a slightly different UI, different copy-paste format, different quirks.

The Invisible Toolkit

Opennomos Json (opennomos.com/en/project/01KJ850Z7PNGXHXESBM68HE12Y) consolidates timestamp conversion, JSON formatting, and Base64 encoding into a single workspace. No install. No accounts. No pricing tiers. Just open a tab and work.

This is the north star for developer tools: make them so simple that the user never has to think about the tool itself — they only think about their actual task.

The Trend Is Clear

We have seen this pattern across the dev ecosystem:

GitHub Codespaces made local IDE setup invisible
Vercel made deployment invisible
Replit made runtime environment invisible

The next frontier is utility tools. The sooner they become invisible, the better.

Try it: opennomos.com/en/project/01KJ850Z7PNGXHXESBM68HE12Y

Part of the Nomos Build-in-Public series.

The Rise of Browser-Native DevTools

ao wang — Wed, 08 Jul 2026 04:28:06 +0000

I spent 45 minutes debugging a JSON parsing error today. Not because the logic was wrong, but because I kept switching between four different browser tabs: one for formatting, one for timestamp conversion, one for validation, one for Base64.

Every tab switch cost me context. Every tool had a different copy-paste format.

The Browser-Native Revolution

We have seen this shift across the dev ecosystem:

GitHub Codespaces replaced local IDEs
Replit replaced local runtimes
Vercel replaced local deployment scripts

But developer utility tools — JSON formatters, timestamp converters, encoders — are still fragmented across dozens of single-purpose websites.

Opennomos Json (opennomos.com/en/project/01KJ850Z7PNGXHXESBM68HE12Y) consolidates these into one browser-native workspace. No npm install. No version conflicts. Just open a tab and work.

Why This Matters

Zero install — your entire team uses the same tooling regardless of OS
Shareable results — formatted output has a URL you can send
Cross-device — works on your phone as well as your desktop

The Future

Browser-native dev tools are not just convenient. They are a paradigm shift — from "tools you install" to "tools as a platform." The same way Notion replaced local document folders and Figma replaced local design files.

Try it: opennomos.com/en/project/01KJ850Z7PNGXHXESBM68HE12Y

Part of the Nomos Build-in-Public series.

Why Online DevTools Are the Next Big Thing for Developer Productivity

ao wang — Tue, 07 Jul 2026 03:14:27 +0000

Every developer has been there: you need to format a JSON blob, decode some Base64, or convert a timestamp. You open your terminal, look for the right npm package, or — worse — write a quick script.

I used to do this too. Then I discovered a better pattern.

The Problem with Local CLI Tools

Local tools have real drawbacks:

Installation overhead: npm install -g some-tool for a one-time task
Version rot: tool stops working after OS update
No sharing: you format JSON but cant send the result to a colleague
Environment drift: works on your machine, not on staging

Online Tools as a Pattern

Opennomos Json (reachable via opennomos.com/en/project/01KJ850Z7PNGXHXESBM68HE12Y) represents a shift: developer tools as a platform, not as utilities you install.

What makes this different:

Zero install — browser tab, done
Cross-device — phone, laptop, any OS
Shareable results — formatted output has a URL you can send to teammates
Timestamp converter built in — ms, seconds, ISO 8601, bidirectional
Base64 codec — no need for a separate site

The Bigger Trend

We are seeing the same pattern across the dev ecosystem: GitHub Codespaces (IDE in browser), Replit (runtime in browser), Vercel (deployment in browser). The next frontier is utility tools in browser.

Why run jq locally when a well-designed online tool does it faster and gives you a share link?

Try It

Head to opennomos.com/en/project/01KJ850Z7PNGXHXESBM68HE12Y — the JSON tools are free, fast, and part of a broader contributor rewards system that makes open-source tooling sustainable.

Built as part of the Nomos Build-in-Public series.

How AI Image Classification Powers Smart Photo Cleanup

ao wang — Sun, 05 Jul 2026 06:35:02 +0000

Every iPhone user knows the feeling: iCloud Storage Full.

When I checked my own device, 68% of storage was consumed by useless images — screenshots, blurry duplicates, near-identical burst photos. Manual cleanup would take hours.

This is where on-device AI changes the game.

How Swipe Cleaner Classifies Junk Photos

Swipe Cleaner (apps.apple.com/id6779493280) uses Core ML to run image classification entirely on-device:

1. Resolution Pattern Detection

Screenshots have a tell-tale sign: they match the exact device resolution. Real photos have varied dimensions. The model flags resolution-anchored images immediately.

2. Metadata Analysis

Camera photos carry EXIF data — location, aperture, ISO. Screenshots and downloads usually do not. The classifier uses this gap to filter.

3. Duplicate and Similarity Detection

Perceptual hashing compares images pixel-by-pixel. Burst photos or saved-then-forwarded memes are caught and grouped.

4. Blur Scoring

A lightweight CNN estimates sharpness. Anything below a configurable threshold gets flagged for review.

Privacy-First Architecture

All processing happens on-device via Core ML and Vision frameworks. No image ever leaves the phone. This is critical for a photo app — users should never have to trust a cloud service with their entire camera roll.

The Result

In testing, Swipe Cleaner reduced photo libraries by an average of 34% in under 3 minutes. The AI does the categorization, but the user always makes the final delete decision.

Key Takeaway

On-device ML has matured to the point where sophisticated image classification can run entirely on a phone, with sub-second per-image latency and zero privacy trade-offs. If you are building a mobile utility, Core ML should be your first option — not your last.

Built as part of the Nomos Build-in-Public series. Try Swipe Cleaner at apps.apple.com/id6779493280

How to Validate a Product Idea Without Writing a Single Line of Code

ao wang — Sat, 04 Jul 2026 04:05:02 +0000

Most founders I know made the same mistake: they spent months building before talking to a single user.

Here is what actually works — and how 01MVP helps structure this process.

The Three-Step Validation Flow

1. Build a Landing Page (Not a Product)

Your first deliverable should be a Notion page, a Carrd site, or a Google Doc. Describe:

What problem you solve
Who it is for
How much it costs

Make it look real. Add a payment link (you can refund later).

2. Manually Service Your First 10 Users

This is the uncomfortable part. Instead of building, you pretend the product exists and manually do the work for each user.

Why? Because you need to observe:

Do users come back?
Do they pay?
What do they actually ask for vs. what you assumed?

3. Only Build After Validation

If 3 out of 10 users are willing to pay for a manual version, you have signal. That is when you start coding — or hire a developer — or use a no-code tool.

The Tool I Use: 01MVP

01MVP (built by the Nomos team) turns this methodology into a workflow: idea → landing page → user feedback loop. It removes the overhead so you can focus on the only thing that matters — figuring out if anyone actually wants what you are building.

The Real Lesson

The P in MVP stands for Process, not Product.

Your first release can be a Google Form. A WhatsApp group. A Notion page. The format does not matter. What matters is whether you are learning from real users or building in a vacuum.

Stop writing code. Start asking questions.

Originally published as part of the Nomos Build-in-Public series.

Stop Reinventing Dev Utilities: OpenNomos Json Is a Clean, Open Toolset That Rewards Contributors

ao wang — Mon, 22 Jun 2026 16:41:39 +0000

Disclosure: I work on Opennomos.

Every developer has that one browser tab graveyard of half-trusted online tools — a timestamp converter here, a JSON formatter there, each wrapped in three layers of ads and a cookie wall. OpenNomos Json is a small attempt to fix that: a clean, no-nonsense developer toolset that just works, and an ecosystem that actually pays back the people who improve it.

What it is

OpenNomos Json is a collection of community-built developer utilities. Two that ship today:

Timestamp Converter — two-way conversion between seconds, milliseconds, local time and UTC, with automatic s/ms unit detection. No more guessing whether 1700000000 is seconds or milliseconds.
JSON Parser — prettify, minify, and pinpoint the exact location of common JSON errors instead of staring at "Unexpected token at position 4172".

No ads. No bloat. Open contribution.

Why it's different

Most "free online tools" monetize you. OpenNomos flips the model: the toolset is built on the OpenNomos platform, where every valid contribution — a new tool, a bug fix, an improvement — earns ecosystem points and benefits. It's infrastructure for computable growth: contribute, use, earn.

If you've ever shipped a tiny utility and watched it disappear into the void, this is the opposite of that. Your idea ships directly, and the contribution is attributed.

Try it

Open json.opennomos.com, convert a timestamp, format some JSON, and if you spot something you'd build better — contribute it. The community grows with what you bring.

Clean tools, open contribution, real rewards. That's the whole pitch.