When building a new communication platform, should I limit users to only 140 chars. Twitter has shown that sharing bite sized information limited to 140 chars is a viable way to communicate. However, when looking toward the future, is this a good thing or bad thing for users? Should I limit them, or should I let them be open ended or some other desired amount?<p>I understand that these can be circumstantial, but what are these circumstances and how do I apply them?
Unless your communication platform is designed to send SMS messages and/or tweets, I'd say a <i>slightly</i> more generous limitation would be better.<p>It is possible for communications to have the virtue of brevity without the need for URL shorteners and abbreviations everywhere.
I agree with respect to mobile device users and they would understand given limitations of text messaging and how they have become familiar with messaging with few characters. PC users will want to explain in more detail and this should be accommodated. That said I suggest not leave it open ended, but some limit so they net their feedback.
Completely depends on what kind of "communication" you're trying to promote. Twitter wanted people to send short, timely messages so they limited message length. How do you want people to use your service? Put constraints on your product to encourage that particular behavior.
I would do the following: for mobile users Yes, for PC's no. And here is why because when they send more then 140 chars on mobile it becomes 2 messages or more (more carrier fees).