Mobile support on Goozex

MOBILE LOGIN PAGE (beta)

Hi all,

We have recently introduced support for those mobile devices (PSP, Treo, Motorola Q, etc.) that were previously not able  to login on Goozex due to javascript limitations. We now offer a new login page in pure HTML that you can use to login from any mobile device that does not support javascript. Once logged in you should be able to see your Request and Library lists (at least).

You can find the mobile login page here: http://www.goozex.com/mobile

Feel free to share your feedback and the list of devices you have been able to test successfully. It will be much appreciated!

Please note: Mobile support is in beta - You may still encounter problems in using the search, advanced search, and some of the My Account/Purchase functions as these use javascript heavily, but most of the other functions should work.

Goozex does not encourages surfing the Internet while driving. Please drive carefully.

 

There is also a user discussion thread here  (that's where the idea / request came from)

I don't post much in the forums (in fact, I think this may be my first one).  But, I wanted to share this since I like the idea of being able to use Goozex via a Mobile connection.  My first impression comment would be this:

 Mobile-intended web pages should not have 135k animated GIFs on the main page!  First, Mobile pages should be short and sweet -- not high in large images (from either an actual size or screen real estate size perspective).  Second, animated GIFs tend to slow down a LOT of Mobile devices still.

Being "Mobile" is not just a matter of whether or not a device support JavaScript.  Many Mobile devices are going to be bandwidth limited/thin.  Therefore, you should do whatever you can to significantly limit the amount of data that needs to be sent.  Having pages that are 300k (which is what the default Goozex Mobile page is) are just way too big.  Look at what the Big Boys (Yahoo Mobile, CNN Mobile) are doing.  You'll see pages that are maybe 10k TOTAL in size -- with maybe some 1k images.  THAT is how Mobile pages should work.

Again, there is a lot more to being "Mobile" than just getting around some JavaScript limitations.  But, again, I like the concept -- so hopefully things will get better as we go...

 - John...

Hey guys, I have a Palm Centro, and all web pages compatible with the Treo are supposed to work with the Centro, but Goozex doesn't.

The page comes out in pieces, which is the only way I know to describe what its doing.
For example.. if its normally organized like this:
               Header               Login
  Systems       Games     Search

on mine it comes out like this:
Header
Login
Systems
Games
Search

Overall, I like having a mobile interface available.  Thank you very much for all your hard work. 

 I just wanted to echo that the page is just a little too big in file size for mobile devices.  Also, it feels a little long in scroll length.

 It would be unfair to just make a criticisim, however constructive, without making specific suggestions...  I'll take a closer look in the next few days and get back with some (hopefully) good suggestions.   Sadly, my cell phone/ Windows Mobile Device doesn't have a very strong connection at home.

 Again, thank you so much for all the hard work on this front.  It is much appreciated.

 Nathan

I agree that the normal Goozex interface is woefully huge compared to the small resolution screens on mobile devices. I put together something like what I would like a Goozex Mobile interface to look like:

http://samuelmcconnell.com/projects/goozex/

Tell me what you think.

To those still looking for a mobile interface, I'm developing one specifically for the iPhone (that also should work well with other devices as long as their browsers support Java). It's in an alpha stage right now but it should be done sometime in May or June at the latest. Search the forums for more info.

taintedzodiac, most mobile devices do NOT support javascript.

Kyouteki:

taintedzodiac, most mobile devices do NOT support javascript.

Ah ok. Good to know. I've never really had a need to try them. Thanks for the info.

Kyouteki:

I agree that the normal Goozex interface is woefully huge compared to the small resolution screens on mobile devices. I put together something like what I would like a Goozex Mobile interface to look like:

http://samuelmcconnell.com/projects/goozex/

Tell me what you think.

 

I really like this, and second the motion. 

Kyouteki:

I put together something like what I would like a Goozex Mobile interface to look like:

http://samuelmcconnell.com/projects/goozex/

 

I really like the idea and the mock up.

We need to do a little more research on what are precise specs for a mobile interface. E.g.: resolution of the screen? HTML standard supported? I'd say that going for a stripped-down, text-only interface is probably a safe bet (like in your mok up). We will evaluate what we can do.

In addition, Goozex will soon release a set of API that will allow this, and other, applications to be built as add-ons or widgets. A mobile version of Goozex could be a very good project to "test the waters" :-)

 

Since I'm something of a self-proclaimed expert on mobile devices, here are some stats:

• Windows Mobile Smartphone: Most devices are 320x240 or (older ones). D-Pad navigation
• Windows Mobile Pocket PC: Most devices are 240x320 or (in Treos) 240x240. Some higher-end are 480x640. Touchscreen navigation
• PalmOS: 240x240, 320x320. 480x480 rumored for future Treos. Touchscreen navigation
• iPhone/iPod Touch: 320x480, multitouch touchscreen navigation

HTML is supported natively on both Windows Mobile phones (Pocket Internet Explorer) and PalmOS phones (Blazer, usually). Most non-smartphones can also render HTML, albeit more basically. If you stick to plaintext and small images, you should be fine. The iPhone of course has Pocket Safari, which is just as powerful as the desktop version and already has no trouble with Goozex.

The things to think about with a mobile site are:

• Keep sizes small, some people have slow connections, and some people pay per kilobyte for data. Minimize both.
• Navigation must be simple, since most mobile users will be using a D-Pad and number pad for navigation. (My mockup probably isn't the best for that, but it was a 5 minute endeavor.)
• Displays are small and usually portrait orientation, so keep text to a minimum length as well.
• Seperate things clearly.

Here's another vote for the slimmed down mobile page.  Today I went to ship a game and forgot the paperwork at the office, so I used my Motorola i920 to access the site and get the address.  All said I think it took me about 7 minutes of browsing and scrolling around on the phone to finally get to the address.

Kyouteki's mockup of the plain white page is perfect, and closely resembles Google's mobile page.  No graphics, clean text and all the useful information in one, easy to access spot.

Thanks for all the hard work!

glad to see the renewed interest in mobile Goozexing :)

I've been finding myself using my PSP more and more these days to browse the web, and while I can do basic Goozex tasks I would love to see more functionality. how about getting part of the forum 'mobile' ?

kudos to everyone for their efforts