{"id":57,"date":"2005-12-31T19:38:52","date_gmt":"2006-01-01T03:38:52","guid":{"rendered":"http:\/\/wapreview.com\/?p=57"},"modified":"2020-09-23T19:44:31","modified_gmt":"2020-09-24T02:44:31","slug":"gmail-mobile","status":"publish","type":"post","link":"https:\/\/wapreview.com\/57\/","title":{"rendered":"Gmail Mobile"},"content":{"rendered":"

Google recently released Gmail Mobile. Given the buzz around Gmail and the fact that Charlie Schick is wondering what my take is on Gmail<\/a>, I HAD to take a look a it.<\/p>\n

First of all, I had no luck getting Google to send me an SMS invite. Supposedly, anyone with a US mobile phone capable of receiving text messages can have an invitation sent to their phone by visiting this page with their desktop browser. Well, it didn’t work for me. I tried multiple times with two different phones on two different carriers (Boost Mobile and T-Mobile). The Google page claimed to be sending SMS’s to my phones but I never received them. I contacted Google support and received a reply that:<\/p>\n

“We’ve investigated, and determined that a problem occurred with your
\nwireless provider. We are forwarding your number to your wireless provider
\nfor further investigation. If you have any questions or concerns, please
\ncontact your provider for more information.”<\/p><\/blockquote>\n
$\"$ $\"$
\nThat sounds like a canned response to me and I’m skeptically seeing as it happened with two different phones on different providers and both phones have no problems receiving SMS from senders other than Google. Nevertheless, I’ve created a ticket with both Boost and T-Mobile – I’ll post if this issue ever gets resolved or even explained.<\/p>\n
Fortunately, I was<\/strong> able to obtain a Gmail invite from www.highwayman.org, a free site where Gmail users can share their surplus invites. I received my invite within a couple of hours after registering – pretty cool.<\/p>\n
Once I got my Gmail set up, I played around with the full desktop version and found it quite impressive. There are plenty of Gmail reviews out there so I won’t go into the details of the full Gmail here. But there are several features that make Gmail different than other email applications. These features make the Gmail experience what is and I was anxious to see how well they were carried over to the mobile version. In summary, in Gmail, on the desktop: $\"$ $\"$ <\/p>\n
\n
Read emails don’t disappear from your inbox until you archive them (deleting emails is discouraged).<\/li>\n
Related emails including replies are grouped into conversations<\/em> which appear as a single item in the inbox, opening a conversation expands it with older read emails that are part of the conversation displayed collapsed to a single line each above the expanded current message.<\/li>\n
A powerfully search capability makes it easy to find old (including archived email).<\/li>\n
Instead of folders, Gmail has categories which work much like del.icio.us tags.<\/li>\n
Instead of rules, Gmail uses filters to selectively treat incoming mail – forwarding, applying labels, hiding Spam etc.<\/li>\n
Many types of attachments (PDF MS Word and Excel, image files) can be viewed as html in the browser or downloaded. PDF conversion is hit or miss, a third of the PDF’s I sent to Gmail displayed as unreadable gobbledygook. PDF’s appear as plain text but Word docs (in full PC Gmail only), while losing images do retain their formatting.<\/li>\n<\/ul>\n
Next, I tried accessing the mobile version at m.Gmail.com. $\"$ $\"$ I had mixed success. Gmail mobile requires a WAP2 device with SSL support. That leaves out all the WAP1 phones as none of the xhtml to wml transcoders handle SSL. Even a lot of WAP2 phones seem to have problems with Gmail mobile. There is a syntax error in the Gmail mobile login screen. The page is sent with an application\/xhtml+xml mime type rather than text\/html so browsers expect the page to be well-formed xml and valid xhtml-mp. The page fails the well formed test as it contains <br> tags – xml requires all tags be closed so <br\/> must be used instead on <br>. Among the browsers that error out on m.Gmail.com are the Motorola, Nokia and Sony-Ericsson WAP2 emulators, Opera (desktop, smartphone and mini versions) and Firefox. IE can’t deal with the xhtml mime type so it fails too. However many users report it working on actual phones and Google has a list of supported phones.<\/p>\n
If Gmail Mobile doesn’t work on your phone there is a workaround. The <br> bug occurs only on the login page. So, do as “minibrand” at the Opera Mini Forum<\/a> suggests: $\"$ $\"$ <\/p>\n
“The following workaround worked for me (I got a parse error on the m.Gmail.com page too):
\n+ open the standard www.gmail.com web page on your mobile and sign in with ‘remember …’ enabled
\n+ go back to the mini start page, without logging out from Gmail
\n+ open m.Gmail.com and you should go into your account.
\n(it should skip the problem page and open in m.Gmail directly).”<\/p><\/blockquote>\n
With the above workaround, most WAP2 phones should be able to access Gmail Mobile.<\/p>\n
So assuming you’ve connected to Gmail, what’s it like? $\"$ $\"$
\nIt’s actually quite similar to desktop Gmail. The first thing you see is the mail in your inbox (first image).<\/p>\n
Related messages are grouped into conversations<\/em> just like on the desktop. Unfortunately, I don’t think conversations scale well to mobile. You have to scroll down a screen or more past the the stacked titles of old read messages in the conversation to reach the new unread message at the bottom (second image).<\/p>\n
Scrolling all the way down to the bottom of the page reveals links for other functions (image 3) .<\/p>\n
Contact Groups<\/em> are supported.<\/p>\n
If you stored phone numbers in contacts, you can place a phone call from the contact screen (4th image).<\/p>\n
Google’s trademark search is there too but not the options of the desktop version to search $\"$ $\"$ specific fields (From, To, etc.) or to search for mail NOT containing the search string or to restrict the search by date or to only those emails with attachments.<\/p>\n
Speaking of attachments, I attached MS Word documents, PDF’s and JPG’s to emails and sent them to Gmail. Two out of the six PDF’s appeared as total garbage on the phone (sixth image) and in Gmail in Firefox on Windows. The problem PDF’s were almost entirely text. The other PDF’s were converted to plain text with all images, fonts boxes and table borders stripped out both on the phone and the PC. At least you are warned :) (image seven). The Word documents also had images removed but while text formating, fonts and tables were retained in desktop Gmail, on the phone they appeared as plain text. JPG’s (eighth image) looked great, resized to 120 pixels wide.
\nIf you have a WAP1 only phone there are at least two ways you can get access to Gmail.<\/p>\n
\n
There is an open source project called Gmail Mobile<\/a> (last four images), a web service written in PHP which provides a WAP1 interface to Gmail. It’s quite full featured with access to your Gmail Contacts and Gmail’s search functions. For maximum security you can download the PHP code from the above address and install it on your own web server. If you don’t have a web server, there is a public copy (hosted by Neerav<\/a>, one of the developers) at Gmobile.sayni.net. The open source Gmail mobile is actually more full featured than Google’s. It has support for the following Gmail features (none of these are supported in the “official” Gmail mobile):
\n– All the search options in desktop Gmail.
\n– The vacation responder.
\n– Creating and enabling filters including conditional forwarding.
\n– Setting up and canceling unconditional forwarding of all mail.
\n– Creating labels.
\n– Adding, deleting and editing contacts and groups.
\nI prefer the way OS Gmail mobile handles conversations. Instead of stacking old messages above the current message as Google does, the OS Gmail puts them on a separate screen, accessed from a link below the current message. One area the Open Source app is inferior to Google’s is attachment handling. You can only view attachments that your phone’s browser has native support for. WAP1 browsers typically don’t support any file types other than wml, wbmp and sometimes text or another image format such as jpg.<\/li>\n
If you have the option to enable POP access on your Gmail settings page (I do but I’ve heard not all Gmail accounts have this feature available yet) you can use mail2wap.com (wml)<\/a> a full featured mobile web based application that can access any POP3 or IMAP4 mail server. Mail2WAP is a service of Mail2Web.com<\/a> a well established service with an excellent privacy policy<\/a> I’m working on a full review of Mail2WAP.com which I should be posting in the coming week or two<\/li>\n<\/ul>\n
In summary, Gmail mobile is a decent WAP based email if you are already a Gmail user and it works on your phone. Gmail as a desktop service has a lot of things going for it. In addition to the innovative UI, Gmail offers features like POP access, forwarding and that huge mailbox limit that other free services don’t. On the other hand, I wouldn’t switch to Gmail based solely on the features of mobile version. It’s a beta, so given Google’s track record, I do expect Gmail Mobile to get better and better.<\/p>\n
Look for my upcoming reviews of mobile Yahoo mail, Hotmail and Mail2WAP – all three of which have advantages over Gmail Mobile in at least some areas.<\/p>\n
Content: $\"*\"$ $\"*\"$ $\"*\"$ Usability: $\"*\"$ $\"*\"$ $\"*\"$
\nGmail Mobile: xhtml<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
Google recently released Gmail Mobile. Given the buzz around Gmail and the fact that Charlie Schick is wondering what my take is on Gmail, I HAD to take a look a it. First of all, I had no luck getting Google to send me an SMS invite. Supposedly, anyone with a US mobile phone capable of receiving text messages can have an invitation sent to their phone by visiting this page with their desktop browser. Well, it didn’t work for … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":21423,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[3],"tags":[],"_links":{"self":[{"href":"https:\/\/wapreview.com\/wp-json\/wp\/v2\/posts\/57"}],"collection":[{"href":"https:\/\/wapreview.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wapreview.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wapreview.com\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/wapreview.com\/wp-json\/wp\/v2\/comments?post=57"}],"version-history":[{"count":9,"href":"https:\/\/wapreview.com\/wp-json\/wp\/v2\/posts\/57\/revisions"}],"predecessor-version":[{"id":21424,"href":"https:\/\/wapreview.com\/wp-json\/wp\/v2\/posts\/57\/revisions\/21424"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/wapreview.com\/wp-json\/wp\/v2\/media\/21423"}],"wp:attachment":[{"href":"https:\/\/wapreview.com\/wp-json\/wp\/v2\/media?parent=57"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wapreview.com\/wp-json\/wp\/v2\/categories?post=57"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wapreview.com\/wp-json\/wp\/v2\/tags?post=57"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}