Debugging is making invisible state observable
Page, logic, network, environment and performance — only when all five layers can be seen is your debugging systematic rather than lucky. With the tools and experience for each.
Blog
Field notes on debugging web pages that only misbehave on a real device — WebView load failures, mobile network problems, storage that vanishes, and the tooling that makes them visible.
PerformanceTooling3 min read
Mobile H5 performance tools compared: chasing a dropped-frame bug
What Chrome DevTools, Safari Web Inspector, Lighthouse and WebDebugX are each good at — worked through a real long-list dropped-frame investigation, so you know which tool belongs at which stage.
Making iOS WebView no longer a black box
How WKWebView's multi-process architecture, caching strategy and cross-origin restrictions hide problems — what causes blank screens, failing requests and lost cookies, and how to debug without a Mac.
The WebView debugging landscape: from vConsole to real-device remote debugging
How to investigate an H5 page that only breaks inside the app — vConsole, Safari remote debugging, chrome://inspect, Charles and real-device debugging arranged into one chain, each covering its own segment.
How do you actually debug a mobile web page?
Mobile is not a browser — it is five wrapped layers: browser, WebView, system, network and performance. Take them apart in order and real-device debugging stops being a guessing game.
22 articles in total