[Windows Phone 7 General] domineus:
So, it's a nitpick to voice some concerns about a method in an OS users are going to use :confused:

That's not the point of the thread at all. It is a thread to discuss some possible cosmetic issues with mango - in fact

And I agree. Last thing I want to do is again scroll through lines of information where services should be separated. the unified messaging idea shouldn't be tossed out, heck it's a bold and genius move. However, the interface is not. You have your opinion, I have mine, the OP has theirs. Guess what, this is a discussion. Why does one argument have to be silenced?

See above comments - its a fricking mess to scroll through all of that crap. And I do mean crap for a few gems...So is there a problem with that implementation? Yes there is. Further, there are several business users that have IM contacts and SMS contacts and they surely don't discuss the same thing. Why do I want it all in ONE conversational view??? It's disorganized, no matter how many different ways its sliced. It's extremely disorganized.

The only person that alluded to technology is you. You're the only person that brought it up, you're the only person that assumed that something is wrong with a user that keeps information via an SMS message. How is that different than keeping meetings/appointments in my tasks or in my email? It's an easy way for me to grab the information if I need it. And to argue that someone is stupid for doing that and then making that argument is contradictory.

Yes let's use the memory that decays information after about 2 seconds as a primary source to memorize important information...that's really smart :rolleyes:

That can work for you, but its completely insipid to expect all users to act like you because frankly they don't.

No one is discrediting that super important information (how to see clients, treat, billing information and so on) isn't important, but to make the argument when I have this device, with a primary purpose to store and recall information that can't be due to me scrolling through crap because my contacts have more than one mode of communication when all it takes is a pivot to separate the modes of communication, I mean come on...seriously?

How is that being lazy if I want something important in a sms and I don't have to remember it and I bought this 500 dollar POS to sorta keep that information? That's one of the many purposes of the device.

And that's the thing - getting on with my life. How am I going to get on in a productive way if I am filtering through thousands of lines of information when it can be better implemented?

And yet a brain is used to point out a possible inconsistency and all you do is call it nitpicking, yet argue people aren't using their brains...

seriously

No one in this threat is knocking the thread idea at all. No one is knocking the idea. What's being discussed is the implementation to the average user. And to be frank, many average users can barely even drag and drop a widget on android. I wish I was making that one up, but frankly, I'm not.

Oh hai

OP said that in the first post >.> way to go for reading...

And yes I did write the article on wmpu. And yes I have received a lot of flack from it. So what? It's an opinion, its a suggestion, it is a discussion. I am not going to blindly say hey this is the best thing since sliced bread if the functionality and implementation can be improved.

I dislike Eldar for his biases and fanboyism. But there is one point he makes

there's a reason why BBM didn't integrate all messaging functions. And there is a point. Implementation.

Microsoft has always had fantastic ideas, I mean ideas that have revolutionized and shape the mobile industry. Their execution hasn't been so lackluster often with companies (apple) using the idea made in microsoft and implementing it differently and making billions.

The main thing is no one wants this to be another one of those ideas that is poorly implemented and I would love to still keep with a unified message system not a unified chat space - BIG DIFFERENCE