Skip to main content

Mix 2011: Windows Phone 7 updates

At the MIX 2011 a lot of announcements were made. So it’s my duty to highlight some of the stuff that is coming to us in the near future.

No long explanation, just everything you need to know about ‘Mango’:

General

  • update is schedule for the fall
  • all existing phones and new phones will get the update
  • 16 additional languages will be supported
  • more countries where we can create apps (from 30 to 38)
  • more countries where we can buy apps (from 16 to 35)

Marketplace / Search

  • better apps list: filter by letters (like with the contacts)
  • new search button to search for a particular app
  • better marketplace
    • more information with less confusion (music and apps are no longer mixed)
    • search for podcasts
    • new “related” pivot item when seeing an app for related app
  • we can integrate an app with the search feature of the phone

Web Experience

  • the update include IE9
  • the core engine is the same code base that the one we found desktop : including HW acceleration
  • address bar is moved to the bottom
  • support background audio for HTML5: you can leave IE and keep listening to the music !
  • tabbed UI for navigating between tabs
  • support for H264 video

Platform

  • improved panorama and pivot control
  • improvements for live tiles
  • access to the ring tones settings (set a music files as ring tone programmatically)
  • TCP/IP sockets
  • SQL database
  • more launchers and choosers
  • data access to the contacts and calendars on the phone
  • better integration with the sensors on the phone (like RAW camera access)
  • Skype coming to the platform this fall (leveraging many of those new features)
  • pin live tiles with deep link to our apps (which would launch the app and give the link as parameter)
  • Silverlight 4 features support
  • applications can now contains both Silverlight and XNA content

Multitasking

  • Spotify coming to WP7 using new multitasking capabilities
  • fast-app switching
  • use “live agents” to prevent battery life

Tooling

  • new version of tools will be available next month !
  • new capabilities in the emulator: simulate accelerometer and location sensors right from the emulator
  • new profiling support

Performance

  • scrolling: totally smooth scrolling without any changes in our applications !
  • image decoding
  • garbage collection
  • memory usage

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...