Leverage Network Debugging to Elevate Your Apps' Performance Quality

on YouTube ↗37m

" summary

Demonstrates using Fiddler Everywhere as a man‑in‑the‑middle proxy to capture HTTP/HTTPS (root cert from getfiddler:8866), run the rule Builder to return 401/500 responses, delay or drop connections, and serve a local file via a VS Code rule so fixes can be tested live. Shows mobile capture steps (proxy port 8866, trust root cert), simulates a 5000 ms delay, exports and shares recorded sessions, and claims debugging time drops from days to hours (cites 1,500 hours annually and ~30% longer to debug than write code).

AI-written summary · about

" chapters (12)

1. 0:00Web debugging efficiency
2. 3:10Proactive debugging for apps
3. 7:43Fiddler Everywhere as proxy
4. 10:28Mobile traffic capture
5. 16:33API/server error simulation
6. 20:13Slow connections & CSS delays
7. 25:10Expired certificates handling
8. 27:17Collaborative bug reporting
9. 29:29Live environment testing
10. 30:56Results and productivity gains
11. 33:25Getting started guide
12. 35:30Q&A

" related talks

• 01h 00mDebugging your website with Fiddler and Chrome Developer toolsRobert Boedigheimer · NDC London 2017
• 01h 01mDebugging Your Website with Fiddler and Chrome Developer ToolsRobert Boedigheimer · NDC Sydney 2016
• 50mDebugging HTTPLorna Jane Mitchell · PHP UK Conference 2014
• 48mMobile debuggingRemy Sharp · Mobilism 2012
• 27mSaimon Sharif - We'll do it live: Underhanded Debugging TacticsSaimon Sharif · React Loop 2019
• 39mDebugging PowerServer 2021 AppsMarco Meoni · ELEVATE 2021
• 27mReverse Engineering a Web APIJoyce Lin · Infobip Shift 2023
• 27m"Lightning Demos"Simon Perkins, Eric Goldsmith, Jaime Yap, Eric Lawrence · Velocity 2010