AlanOfTheBerg wrote:psychomf5 wrote:Please make this...
Go vote for it.
RallyChris wrote:Please understand, that win phone 7 is a completely different platform, so this is not as simple as recompiling and deploy.
unwallflower wrote:dalydose wrote:RallyChris wrote:Please understand, that win phone 7 is a completely different platform, so this is not as simple as recompiling and deploy.
Are you suggesting that we shouldn't express our desire to have waze? If not are you saying that it hasn't been enough time, because lots of other companies have found a way to make it happen by now.
Maybe you are saying that the "numbers" don't add up to making it worth it. Counter argument made better than I can here: http://www.businessinsider.com/why-deve ... -7-2010-10
The bottom line is that there is an army of potentially passionate evangelists out there that waze is missing out on. These are loyalists and people that USE the heck out of their technology. They would be good for the waze ecosystem which provides the precious data that would be a boon to waze and all of its users on all of its platforms.
Sure it's a different platform, but they made it happen with Android and originally with iPhone. I've heard that it is one of the easier platforms to develop for and there is compelling evidence that it is worth the effort. I just hope some MBA type at waze figures it out and makes something happen.
I don't think that RallyChris was implying that you shouldn't express your desire for a WP7 client, OR that it "isn't worth it" at ALL. I didn't see any such argument from him.
He was simply saying that it's not like designing a client for Android 2.1 vs Android 2.2. It's an entirely different OS, and therefore my impression is that the level of effort required to design a WP7 client would be similar to if they decided to design a client for your laptop. They wouldn't have to just tweak the code a bit, they would have to rewrite it entirely.
Waze is still sort of a "baby". They have limited staff. Face it, if you look around the forums... they can't even keep up with developing for iOS, Android, Symbian, and Blackberry, AND maintain their server-side systems. It's my impression that they just don't have enough manpower. I think RallyChris was trying to say that developing for WP7 would be a significantly greater undertaking than many users seem to understand. When you have limited resources, you have to allocate them in such a way that makes the most sense... and it looks like Waze has allocated their man-resources in the way that makes the most sense to them.
unwallflower wrote:I think you have a good point, and I can't argue against it. Getting Waze to the widest audience possible, especially in situations where it may be the best/only nav app, seems ideal. And given past experiences with Waze, I'm surprised that this isn't their goal.
I certainly don't always agree with their priorities. I wish I knew what prompts them to allocate their time in the way that they do.
Mscatinboston wrote::o OMG, I just switched to W7 with Verizon. I did not realize that I could not use Waze. What am I going to do without my Waze!
unwallflower wrote:TBH, it doesn't surprise me *too* much that the devs are choosing to (at least temporarily) neglect Windows Phone 7.
WP7 simply isn't the "future" of mobile devices. And I know some of you loyal WM users will disagree with that, but it's what I strongly believe.
Not to mention that Windows Phone 7 isn't just a new iteration of Windows Mobile... it's an entirely different platform. WP7 can't run WM apps. I think it would require a lot more work than some might think.
Users browsing this forum: Google Feedfetcher