Build 2015: ShoppingDemo

I wanted to really quickly make a note that the first commit of my Build 2015 demo is now up on If you’ve been following me on Twitter (@aruntalkstech) you might know that I plan to build my Build demo in my GitHub repository. The code in there should build with the latest Windows 10 preview tools but not all of it runs flawlessly on 10041 or 10049. So while you can play around with it be wary of not implemented exceptions and other places you’ll fall off a cliff because we’re not done yet. Still, great way to explore what’s coming.

Here’s a quick back of the envelope map of the world showing what’s interesting in there:

I’ll have more details as we continue to build out this demo. Feedback/Comments are very welcome. Leave them here or tweet them @aruntalkstech. Happy hacking! 🙂

9 thoughts on “Build 2015: ShoppingDemo

  1. What I’m wondering is – will the OS launch the Store app and prompt user to install the app/app service if it’s not already installed when you try to use it?


    1. Also, when you try to set up a connection and fail – you simply Debug.WriteLine(“Failed to open connection: ” + status.ToString());
      It would be good to establish a more user friendly standard for how to respond to these. What are possible failure reasons? How would an app typically respond? Not sure what the possible status codes are, but a switch block would be nice in the sample.


      1. I intend to talk about the failure reasons during my //Build session. The goal is to keep the demo relatively simple until Build so it’s easy to get into for someone who’s just taking a quick look.


    2. Not for app services because it would be weird to suddenly see a prompt asking you to install an app that the app you’re using was trying to launch in the background. Instead, we tell you whether or not the app service you’re trying to connect to is available so the app developer can offer to take the user to the store if they want to.

      For launcher, we’ve always offered to take the user to the store to find a suitable app and we’ll continue to do that. If you specified a LauncherOptions.TargetApplicationPackageFamilyName (that’s a new property) we take the user to the store page of the app identified by the TargetApplicationPackageFamilyName.


  2. Hi, what happens when my app calls LaunchUriForResults and while the other app is running, my app gets tombstoned?


    1. On mobile, your app gets suspended. That is, it still runs but because the app you launched is in front of the user your app gets no CPU until the user is done interacting with the app you launched. On desktop, both your app and the app you launched keep running because the user can see both. Does that make things clearer?


      1. What happens on the phone when the new app launches another app, that launches another app… until the phone runs out of memory? Do any of the apps along the way get tombstoned (which would mean that awaiting the LaunchUriForResults would not finish, because the app gets killed).


      2. We do a bunch of memory compression on suspended apps (on mobile) to try and make this as unlikely as possible. But you’re right, at some point along the way if you send the user 5-6 levels deep the original caller will get tombstoned So far we’ve tested this scenario with up to three apps on low memory (512MB) devices with good results. In general my recommendation is that apps launched for results should not (if it can be avoided) launch other apps for results.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s