Shiny HTTP Transfers: Why Is This Data Still Not Here?
Somebody is waiting on bytes that were supposed to have arrived. Usually nothing was carrying them — HttpClient stops the second iOS suspends your app, and Android will reclaim the process while you are not looking. Shiny.Net.Http hands the bytes to the platform instead — NSURLSession, a foreground service, a connectivity-driven managed loop, Service Worker Background Sync — under one API. Plus why I sign Azure Blob and S3 uploads by hand instead of taking the vendor SDKs, what the Android service does when the network drops, and why a Live Activity has to animate a time range instead of a percentage.