Today, Shawn Wildermuth, who has written six books on .NET and is heavily involved with the Microsoft ecosystem (so yeah, bias), discusses his thoughts on Android. He's uses a Motorola Droid on Verizon as his daily driver and just updated to OS 2.2 aka 'Froyo'.
One of his choice quotes would be
...But there is an intrinsic problem here. I had to use some spelunking to find out what background processes were killing my performance. This is a big bucket of FAIL.
Phones aren't for geeks, they are for regular people like my mother and my sister. The fact that most Android users learn to use a task management app means there is something wrong.
We couldn't agree more and while we hope Windows Phone 7 v1.0 moves beyond the current feature-incomplete status sooner than later, we're quite happy with this new direction and focus on consumers.
...the notion is that Verizon is dropping everyone and just going 100% Android? While we have no doubts Verizon is doing a big push with Google, we find it hard to believe that they have no use for RIM's Blackberry anymore, let alone Windows Phone 7.
Our source says that the fallout from this troubled partnership is that Microsoft has backed away from Verizon as a Windows Phone 7 launch partner, claiming that the first handsets you see won't be offered on the CDMA carrier -- rather that we should expect GSM partners to get first crack.
In this case, the tables are reversed with Microsoft being the one to back away from Verizon, partially due to their poor handling of the KIN (e.g. jacking up the cost on the data plan).
Our thoughts? Sure, anything is possible. Verizon is clearly in love with Android, but their "roadmap" seems incomplete to our eyes. We also think that sales make the deal and if Windows Phone 7 does well, Microsoft and Verizon will warm up to each other and work out their differences. After all, not everyone was thrilled with Android either. Finally, the lack of evidence doesn't mean we can just fill in the blanks with our own speculation. Lets wait and see what happens, eh?
Though rather large and blocky, the device seems to feature, unsurprisingly, an AMOLED screen. Due to the Twitter's location, we're betting this isn't necessarily a device for the U.S., but who knows what Samsung has up their sleeve.
While seemingly impressive, it was a drop in the bucket compared to the number of developers who need a device.
Well, if the latest Facebook registration numbers are to be believed, that number has doubled and is now at roughly 6,483--pretty impressive. How high will it go? We have no idea, but at least we know Microsoft is trying to seed these devices as quickly as possible.
Edit: Or as Matthew Miller (Nokia Experts) notes in comments, instead of 6.000+ phones, perhaps we're looking at the same 3,000 but in new hands as developer/tech preview units have had to be returned.
Busy if not unexciting day for HTC leaks so far...
First, it appears that those earlier pics of the HTC Schubert were mis-identified. Instead, it seems that it is actually the HTC Mozart, a more low-end WP7 device headed for Telstra (rumored for T-Mobile too). A few more non-thrilling images are below via Xmoo on Twitter (as evidenced by the low-quality images, he must be using an HTC camera--zing!)
So for those thinking "Is that all HTC's got?", the answer would be "???".
We're still waiting for the big guns from HTC but at least appreciate the fact that Windows Phone 7 will be on a wide-range of devices/price points--well, as wide a range as "black slab" can go at least.
Congratulations and braggin' rights goes out to WMExperts member arthurbrownleeiv for winning the BlueAnt T1 Bluetooth headset. His post in our forums discussion was randomly selected to win the headset.
Congratulations also goes out to jh20001 for being selected as our Giveaway Runner-up. jh20001 will be receiving the Maximo iMetal Stereo headset.
WMExperts.com would like to thank everyone for participating in this Giveaway Contest and for sharing some great looking home screens. We'll keep the discussion going and while the contest period has come and gone, feel free to show off your Windows Phone home screens.
We recently reviewed the BlueAnt T1 Bluetooth headset and found it to be a nice, rugged headset. We haven't had a giveaway in a while, so what better time than the present.
It's also been a while since we did a "show us your home page" discussion over in the forums. So we decided to kill two birds with one stone. If your interested in winning the T1, simply head on over to this Forums discussion and share your home screen. If you're not sure how to capture your home screen there are tons of methods such as MyMobiler or Shake and Save.
We'll let the discussion run until 7:00pm PST on August 11, 2010 and randomly choose one post to win the T1. You do have to register to participate (a painless process that starts here) and we'll post a "braggin' rights" announcement later that week.
UPDATE: Seeing that it's been so long since we've had a give away, one prize just didn't seem to be enough. While the first prize will remain the T1, we'll choose a second post at random for a Maximo iMetal Stereo Headset.
Want a DIY app maker for Windows Phone 7? Better yet, what is a DIY app maker?
To answer the latter, it's basically a program to write programs that assumes you know nothing about programming. Case in point: Google's Android App Inventor.
On the one hand, it's hella cool, especially if you're like us and know nothing about C#, XNA or Silverlight.
On the other hand, it results in things deemed 'crapps' by our esteemed colleague Phil (see above article).
One twist? We have an approval process in our app store, so more than likely the majority of 'crapps' won't be approved, but once we figure how to 'sideload' you can use your crapp...err app as you see fit and probably even share it.
All of this will soon be made possibly by Jay Desai who is in the middle of writing an app to do just what Google has done--though perhaps not as smooth. As of right now, the app is just a technical preview, yet it still has RSS Feeds, Facebook, Twitter feeds and may add YouTube and Flickr support in the future. This will allow you to write apps that interact with those feeds, making it pretty neat.
Sounds interesting? Try it right here though you'll need a password, since it's still in development: You can request a temp password via Twitter @desaij