4 ms·

Charles can already be used as an http/https proxy on iPhone via https://www.charlesproxy.com/documentation/faqs/using-charles-from-an-iphone/ https://www.charl

Charles can already be used as an http/https proxy on iPhone via https://www.charlesproxy.com/documentation/faqs/using-charles-from-an-iphone/ https://www.charlesproxy.com/documentation/faqs/using-charle... I generally would only be needing to inspect requests when developing at my workstation, so how is this native app providing additional value beyond what the Charles Mac software already provides? Big fan of Charles over here, I just don't understand the use case for the native app.

dc3k 9y ago
>I just don't understand the use case for the native app. I can't use Charles to inspect traffic from my device at work because of network restrictions. Now I can.
eridius 9y ago
You can't use the Mac app to inspect any requests that go over the cellular connection. Using the Mac app also requires being able to connect to your Mac from your iPhone (in order to use it as a proxy), which is not doable on many setups. For example, at work we use a different wifi network for mobile devices than we do for laptops.
trevor-e 9y ago
Straight from the announcement: "Running Charles on your iOS device means you no longer need to fiddle with WiFi network proxy settings. It also means that you can capture and measure network traffic that goes over the Mobile / Cellular data network. Measuring networking performance over Mobile data is especially important for your mobile apps (as that is how a lot of users experience your app), and it can reveal large or slow requests, as well as opportunities to increase perceived performance by parallelising network calls." AFAIK before this you could only inspect traffic over WiFi connections since you had to set the proxy address via WiFi network settings.
dorian-graph 9y ago
> I just don't understand the use case for the native app. You can watch his presentation [1] (which is linked to in the announcement page that story links to) for a few of the use cases. [1] https://www.youtube.com/watch?v=RWotEyTeJhc https://www.youtube.com/watch?v=RWotEyTeJhc
dsl 9y ago
I've had to do audits of apps that required you to be connected to a specific Wifi AP (usually with a dev server instance attached) to function.

dc3k 9y ago

>I just don't understand the use case for the native app. I can't use Charles to inspect traffic from my device at work because of network restrictions. Now I can.

eridius 9y ago

You can't use the Mac app to inspect any requests that go over the cellular connection. Using the Mac app also requires being able to connect to your Mac from your iPhone (in order to use it as a proxy), which is not doable on many setups. For example, at work we use a different wifi network for mobile devices than we do for laptops.

trevor-e 9y ago

Straight from the announcement: "Running Charles on your iOS device means you no longer need to fiddle with WiFi network proxy settings. It also means that you can capture and measure network traffic that goes over the Mobile / Cellular data network. Measuring networking performance over Mobile data is especially important for your mobile apps (as that is how a lot of users experience your app), and it can reveal large or slow requests, as well as opportunities to increase perceived performance by parallelising network calls." AFAIK before this you could only inspect traffic over WiFi connections since you had to set the proxy address via WiFi network settings.

dorian-graph 9y ago

> I just don't understand the use case for the native app. You can watch his presentation [1] (which is linked to in the announcement page that story links to) for a few of the use cases. [1] https://www.youtube.com/watch?v=RWotEyTeJhc https://www.youtube.com/watch?v=RWotEyTeJhc

dsl 9y ago

I've had to do audits of apps that required you to be connected to a specific Wifi AP (usually with a dev server instance attached) to function.