- Jan 14, 2011
- 931
- 5
- 18
Forgive me if I am wrong, im not a dev. But if MS is telling all devs to update their apps ASAP... NOW... doesnt that create a problem for devs if Mango is delayed through Fall?
I read about the requirements for developing for WP and any change creates a build number change. Once these devs use the SDK to make their apps "mango compatible" for the "multi-tasking/instant resume" to work... if Mango is delayed that means the update will not launch to non-mango phones.
Joe says "Fall" which could mean from this Thursday through Dec 21. IF the later becomes the case, does this mean devs cant release ANY updates because the build number has increased for the app's mango update? In which case if they discover a major flaw in their app, they would not be able to do anything about until Mango is released. (?)
I cant see that MS would do that to the devs. Telling them to update their apps to Mango NOW and then push the launch back... Fall? Nov 15, or Dec 20.
I read about the requirements for developing for WP and any change creates a build number change. Once these devs use the SDK to make their apps "mango compatible" for the "multi-tasking/instant resume" to work... if Mango is delayed that means the update will not launch to non-mango phones.
Joe says "Fall" which could mean from this Thursday through Dec 21. IF the later becomes the case, does this mean devs cant release ANY updates because the build number has increased for the app's mango update? In which case if they discover a major flaw in their app, they would not be able to do anything about until Mango is released. (?)
I cant see that MS would do that to the devs. Telling them to update their apps to Mango NOW and then push the launch back... Fall? Nov 15, or Dec 20.