| |
|
By Ellen Isaacs This page last updated: September 13, 2000
To initiate a text message, the user taps on the name of the person from the Hubbub main screen. This brings up the Bub screen for that person, as shown in Figure P6. To start an instant message, the user types a message into the text area at the bottom of the screen and taps "Send." If the other person is accepting text messages from this person, the Text Message screen appears on the user's screen, as shown in Figure P7. Figure P8a shows a conversation that has already been in progress. Each time a user send a message, that message appears at the bottom of the scrolling area and the rest of the conversation scrolls up. The user's comments are in regular type and the other person's comments are in bold. The header of a TIM indicates the time at which the conversation was initiated, it does not update with each new contribution. Users can also send Sound Instant Messages as part of their text messages.
To save on memory, the TIM screen does not retain a history of all the messages in a given conversation. Instead, the last 100 messages (from either person) are available, but if the user tries to scroll back beyond that, the messages are no longer available. To end a conversation, the user taps the Done button. They are returned to the main screen, showing whatever group was last displayed. When a user receives a text message, the incoming text message sound plays followed by the sound of the person sending the message. In addition, the text message window automatically displays on their screen except for a few cases. Namely, if they are already in a conversation with someone else, then the newly created conversation appears in the IM menu and the number next to the menu changes to reflect the new conversation, but the screen does not switch to the new message. To see the new conversation, the user pulls down the menu and switches to it. The other exception is when the user has a blocking popup on their screen. These appear when the user is in the middle of some action and needs to provide input to complete it, e.g. adding a user, changing the name of a group. In this situation, the sounds play when the message arrives, and as soon as the user closes the popup, the incoming message appears. [Might be better to give it something like two seconds so they can see that whatever they were doing took effect before being moved off. We'll probably need to tweak this behavior, since it's very annoying to have things happen when you're in the middle of something else.] Each time the person sends a new message to an existing conversation, just the TIM sound plays (without the Sound ID of that person). [Maybe you hear the SID if you're not looking at that window, or maybe SIDs only announce new conversations. We could also do something to show which message has unseen contributions, e.g. make that name in the menu bold, to help you Figure out which message to look at next.] The TIM screen provides information about the other person's focus and activity in their TIM window with this user. Specifically, an icon to the right of the bub's name indicates which of three states they are in: (a) typing in this IM window, (b) viewing or has focus in this IM window but is not typing, and (c) not viewing (Palm) or does not have focus (desktop) in their window for this exchange. As the other person switches between different states, the icon updates to reflect this information. Figures P8a and P8b show the icon for "focus in the window," and "typing in the window." The menu in Figure P9 shows all three states, including "no focus in window." This TIM activity indicator enables people to coordinate their conversation, which is bound to be punctuated by pauses given the speed at which people can write on the Palm. Users can interpret whether the long pause is because the other person is composing a long response or because they're busy doing something else, and then adjust accordingly.
When the user returns to the conversation, everything appears as it did before, with perhaps additional messages at the bottom if the bub has entered any. If the user wants to end the conversation, they tap the "Done" button on the IM window. (This is the equivalent of closing an IM window in the desktop world.) The conversation no longer appears in the menu and there is no way to "get back to it." However, note that the other person may not have "closed" their end of the IM. If they send a new message, the recipient experiences that as a new conversation being started from that person, with a new initiation time and no history of previous messages.
If the user tries to send a text (or sound) message to someone who is offline, then a window pops up, as shown in Figure P10. Since the would only get the screen if they had already typed a message into the text field first, that message is provided in the text area so the user can either send it as is, or modify it and then send it by tapping the Send button. When it arrives in the recipient's inbox, the Subject is "Hubbub message from {Bubname}." Since the message must be short, the interface allows only 512 characters. If the user tries to write more, the character is not echoed and the interface beeps. [Note: if scrolling doesn't come for free on this screen, then the message can be only as long as this interface allows, which is about 170 characters. We will not implement scrolling just for this window.] If the user taps Cancel, then they are returned to that Bub's Bub screen. |