Best background processing/API call approach?
<p>I've come up with two different approaches for handling an API call off the main UI thread, and I'm wondering which one is better in terms of performance or resource allocation. These are Android-specific examples, but I have a similar setup for iOS as well, so looking for an answer with cross-platform consideration.</p>

<p><strong>Option 1</strong> - Kick off a new thread for the request, and handle response in the callback on the UI thread:</p>

<pre><code>    apiTestButton.Click += delegate
    {
        progressBar1.Visibility = ViewStates.Visible;

        new Thread(new ThreadStart(() =&gt;
        {
            string response = Core.BLL.API.GetJsonTest();

            RunOnUiThread(() =&gt; ApiTestCallback(response));
        })).Start();
    };

    void ApiTestCallback(string response)
    {
        progressBar1.Visibility = ViewStates.Invisible;

        Toast.MakeText(this.ApplicationContext, "API response: " + response, ToastLength.Long)
             .Show();
    }
</code></pre>

<p><strong>Option 2</strong> - Leverage async/await:</p>

<pre><code>    apiAsyncTestButton.Click += async (sender, e) =&gt;
    {
        progressBar1.Visibility = ViewStates.Visible;

        string response = Core.BLL.API.GetJsonTestAsync().Result;

        progressBar1.Visibility = ViewStates.Invisible;

        Toast.MakeText(this.ApplicationContext, "API response: " + response, ToastLength.Long)
             .Show();
    };
</code></pre>

<p>Using async/await, the code is obviously a bit more concise - no need for a separate callback method. But I'm wondering how these two options stack up in terms of performance. I assume Xamarin will translate/transform C# into platform-native logic (iOS and Android), but which would be easier for it to handle and are there performance implications?</p>