4 votes2 comments · Universal Windows Platform » XAML/Controls/Composition · Flag idea as inappropriate… · Admin →
This isn't possible given WP's security model. The WebBrowserTask launches the Web Browser application, which doesn't have access to your application's Isolated Storage.
Happy to report that we are making the splash screen optional via a declaration in the UWP app’s package manifest. Tim Heuer and I talked about this at Build 2017. This is targeted to ship with the Fall Creators Update and we will be testing and tuning the timings via flights to Windows Insiders. To opt in, you simply set the property Optional=“true” on the SplashScreen element in your Package.appxmanifest in your app project. If your app is alive and kicking prior to a TBD timeout value, then users don’t see the splash screen. Otherwise they do.
While I don't disagree with your general request, have you looked the (Microsoft) weather application? It's Silverlight and it starts reasonably quickly (pretty much on par with the people hub)
This is a user feature, not a development feature
Thank you for the suggestion and the spirited commentary. We are not adding this capability in the 8.0 release, but know that it is high on the consideration list for future Windows Phone releases.
I am familiar with ShareStatus/Link, but they don't include custom features such as "like" or accessing the user's friend list. The core API will never be able to match the Twitter/Facebook/LinkedIn SDKs feature-for-feature, so allowing the application to obtain an access token (with user approval, noting permissions) would allow them to do more.
Even the official Facebook/Twitter applications forces you to re-authenticate - it doesn't make any sense.Richard Szalay shared this idea ·
With touch events being moved onto another thread in Mango, you should see an improvement in perceived performance. If not, try to simplify your UI (complex layouts are more expensive).