IMHO, I find it useless. Maybe for long messages (splitted, >500chars) in East-European languages it's a good idea, but not for any Western European language (English, French, Spanish... yeah, it's maybe a little bit slower to write but not a pain, at all).
Anyway, the whole process (open the app, write in my computer then copypaste to the message app) is slow and painful. It would be "better" to have an associated username (with password) in the computer+in the iPhone. For example: I open the app, I write in my computer that long-long message, the app automatically updates (COMET anyone?) and I just tap a "send" button, which opens the message app with the message already written...
... but in fact, the whole idea is pretty useless, we don't write messages as we write emails. And for emails, we already have another way to do it :-)
I agree that the process (open app -> enter code -> send message -> paste) is a bit cumbersome but still I can't cope with the onscreen keyboard for message longer then a few chars. I still think that somebody out there feels the same pain, sale stats will tell us the truth :)
The next release will have a "persistant pairing" flag that will allow users to skip the "enter code" phase to make the process a bit faster.
Unfortunately opening the app with the message already written is not possible with the current SDK :(
Comments
IMHO, I find it useless. Maybe for long messages (splitted, >500chars) in East-European languages it's a good idea, but not for any Western European language (English, French, Spanish... yeah, it's maybe a little bit slower to write but not a pain, at all).
Anyway, the whole process (open the app, write in my computer then copypaste to the message app) is slow and painful. It would be "better" to have an associated username (with password) in the computer+in the iPhone. For example: I open the app, I write in my computer that long-long message, the app automatically updates (COMET anyone?) and I just tap a "send" button, which opens the message app with the message already written...
... but in fact, the whole idea is pretty useless, we don't write messages as we write emails. And for emails, we already have another way to do it :-)
Thanks for your feedback!
I agree that the process (open app -> enter code -> send message -> paste) is a bit cumbersome but still I can't cope with the onscreen keyboard for message longer then a few chars. I still think that somebody out there feels the same pain, sale stats will tell us the truth :)
The next release will have a "persistant pairing" flag that will allow users to skip the "enter code" phase to make the process a bit faster.
Unfortunately opening the app with the message already written is not possible with the current SDK :(