davux

I didn't port (and wouldn't for the MMS/landline issues alone, I think) - I did it all 'on top' of an at&t and an ipkall.com/SIP/asterisk number.

I used to be a huge fan of Google Voice, but I'm not so hot on it anymore. I started using it because I didn't have good at&t reception at my house. It was a godsend at first, I could actually get text messages without having my phone in a very specific place.

But as I continued to use the service...

- Not having MMS shouldn't be a big deal, and it isn't. Until someone wants to send you one. "Oh no, send it to my other number, sorry about that. Which number? Oh, you told me not to text there, so I deleted it." But then people start sending everything to that number, and you have to tell them which number to use for what thing. People hate this, and I don't blame them--it gets confusing.

- GV is seen as a landline, goodbye all of those cheap m2m minutes, you're now costing your friends part of their anytime minutes even though you're actually talking to them on your cell phone. This isn't a huge deal, except for those people that don't have many anytime minutes--because they mostly only call cell phones. I'd love to know whether this is a problem when you port your GV number to Sprint, but I have no idea.

- GV will sometimes drop SMS forwarding. I miss around 1 message a week (call it 1 in 1000), it'll show up on google.com/voice, but it never makes it to my phone.

- For several years, all the Google forwarding numbers (the numbers that you will get an SMS from, a unique number per contact that is generated the first time they send you a message) were in the 406 area code. This made it pretty easy to always be sure of which number you were sending to. Last year, they started assigning numbers based on any area code. This means you must be very rigid in how you add phone numbers to your contacts. It gets confusing when you have a contact with two SMS-capable numbers, now you have 4 numbers (Home, Work, Pager, Home Fax?). This is a big problem if you sync with Exchange, less so if you can assign custom number labels (Home GV, Work GV, etc.).

- Sometimes messages are delayed. Perhaps once a month I'll start getting messages delayed by an hour or so. This happens with cell carriers too (although I rarely see it on that side), so not as big of a deal as dropped messages.

- I won't even get into the lack of an API and the frustration that causes for those that choose to write apps that utilize or extend GV.

After years using GV, I now have a MicroCell at home, and I've switched everyone back to my at&t number. It's just less confusing. I've wanted to love GV so badly, but it just isn't the silver bullet that it is advertised as.

Maybe Google will fix Google Voice, but I'm not as optimistic as I used to be. :(

I agree with you and I don't feel that QR codes are a good fit for things like this (it's just awkward), but just a small nit: Windows Phones actually do support QR codes (and other bar codes) out of the box. I'm sure there are others, but that is the only know I know of. :)

I really liked the idea of Chrome to Phone on Android, so I built Send to WP7 for Windows Phone. I kind of feel that using SMS is really only a good fallback solution for phones without a good app (not to mention removing the need for cell signal, etc.). Cool project though, a great use for Twilio. :) Nice job!

It says "Total Login Hour Options (Limited Time Discount!)" for the anytime access--so it seems that it normally costs more.

Still a pretty complex pricing model, wonder what they're doing on the backend to swap sessions around.

The whole point of that song was that everything seemingly ironic was NOT in fact ironic at all. :)

They don't match though. Search = (search?), Menu = App Switcher?

I'm sure it won't block upgrades, but it's definitely at least a little bit awkward. I'm also wondering what apps will look like with the menu button--is there a 4th added onscreen? Then how does the hardware/software button mapping work?

Android really doesn't run quicker than WebOS yet. There isn't any 2D hardware acceleration (last I knew, a few days ago). This means that sometimes Android is really fluid, but then it starts studdering and kind of ruins the experience.

I also had a ton of Force-Close's on the browser. I'm back to WebOS until the Android CM7 builds get past Alpha. It looks like it'll be usable, but not really yet.

IE9 on Windows 7 and IE9 on Windows Phone Mango (7712) also score 100% now.

So using colors is bad? What is the right way to do inline? Or is the problem that Exchange wouldn't let your Linux client get the full version?

I'm confused as to why this is really a big problem. Sometimes, people really muck up replying inline, and it is somewhat harder to find their comments, vs. having their comments completely seperated from the previous message. Perhaps it depends on the class of user that you are serving, as well.

I just wanted to say thanks. :) As a person with low vision (and a heavy VS user), I'm grateful that there was so much attention to detail in the development of VS with respect to accessibility.

I don't know if it has to do with US government ADA requirements or not, but I'm glad that across the board Microsoft tends to build accessible software.