conanheath
New member
Completely disagree. The strategy is sound, they just need to execute faster.
Their strategy is slow, slower and slowest. How is that a good strategy?
Completely disagree. The strategy is sound, they just need to execute faster.
that maybe true but when a phone is lunched it's compared to what the current OSes are out there. I cant compare WP 8 to iOS 4 that was like 2 years old that doesn't make sense. compare current to current.
You've never done
Commercial Products
Software
or
Service
development, have you?
Every company that makes any product that competes with other products has
A roadmap of when new features will be added
A list of compete features where they are ahead, at parity, or behind the competition
A list of known deficiencies (ie, bugs).
A list (usually ranked) of customer feature requests.
Product managers balance their budgets for putting resources into all four of those. The weighting of the choices varies at any given time - when feature parity is a goal, more effort goes into adding features that are missing. When differentiation is the goal, adding new unique features is a priority. When bugs become a problem, more effort goes to bugfix.
The "reasoning" is business 101. The platform has a small market share, and not much feature parity - there is a heavy focus on differentiation. Not to mention that the whole platform had to be moved three times (WinMo -> WP 7x -> WP8) which soaks up a lot of effort.
Their strategy is slow, slower and slowest. How is that a good strategy?
Just want to point out the early days of the iPhone, the one that came out without 3G in 2007, there was no app store. No cut and paste. No SDK. No developers. It took a year to get an SDK and um nearly two years and two full OS revs to get cut and paste into iOS
iOS Version History: A Visual Timeline | Visual.ly
Let's not forget that just because you're behind doesn't mean you can code awesome faster.
Just want to point out the early days of the iPhone, the one that came out without 3G in 2007, there was no app store. No cut and paste. No SDK. No developers. It took a year to get an SDK and um nearly two years and two full OS revs to get cut and paste into iOS
iOS Version History: A Visual Timeline | Visual.ly
Let's not forget that just because you're behind doesn't mean you can code awesome faster.
Their strategy is slow, slower and slowest. How is that a good strategy?
They released a completely new kernel in an insanely quick period of time...
I don't think they are slow at all in the big picture but many of you are speaking about tiny feature lists which they do take too long to implement.
They released a completely new kernel in an insanely quick period of time...
I don't think they are slow at all in the big picture but many of you are speaking about tiny feature lists which they do take too long to implement.
This maybe true if Microsoft didn't come out and said wp8 was already in work even before wp7 was released
...but I just can't get why those basic features' importance/resources needed are so low internally in MSFT.
Microsoft's Windows on ARM project existed long before WP7 was released...
If u go back to the earlier days of iPhone, even iPhone4 on iOS4, u will see that it was a common thing - so if u volume down the music, or the game, u do the same to ur ringer...
i'm confused as to where you're going with the point.
Your explanation totally makes sense from a "software developing" point of view, but does it if you look at it from a market perspective?
<snipped>
Given that, my answer is that they have to invest more to keep the customers happy, even if this means throwing away money in features that will be obsolete in 9 months.
Am I hallucinating?
Creating a massive app store that no one had even done before is 10000x more difficult than fixing small holes that others already fixed. To be honest, if it was Ballmer not Jobs created the idea for cellphone app store, the idea would be forgotten in backyard now.
And I agree with somebody in another post, "compare current to current". Fanboys can always find excuses but market don't.
I can't really answer your question, because I don't know much about their budgets. All I know is that they are already investing hundreds of millions every month, and that Google, Apple and Microsoft are all rather good at doing cost/benefit analysis... better than I am.
I also know that developing anything significant, something that is actually able to change consumer perceptions, requires major investments... hundreds of millions. If that were my own money, I wouldn't be too enthusiastic about investing it into throw away software no one will remember in 9 months.
Calling for MS to throw more money at a problem is simple. Very likely too simple. That is what I think.
The point is Apple's execution isn't any faster than Microsoft's.
From my personal "cost/benefit" analysis, looks to me that with very little investment, they could fix a whole lot of issues in a very short time...