Jump to content
Dj's United

Recommended Posts

Guys and Girls,

 

I've recently starting thinking about making a MOBILE site... for mobile phone users!

I am going to insert a redirect script once it detects a mobile so it will auto show the mobile version.

 

But I need some help! :)

 

I've only created the front index page... with NO links so far to any other pages....

 

http://www.alexentertainment.co.uk/site/iphone/index.html

 

If possible, could some of you visit the site and tell me if it appears nicely on your screens?? - Please bear in mind, it's a very basic site... so it's not flashy or zazzy!

 

Also let me know which type of mobile phone you used to access it?

 

xx thank you very very very much in advance xx

-------------------------------------------

Web : http://www.alexentertainment.co.uk

Web : http://www.alexskaraoke.co.uk

Phone : 07525 645750 / 0800 612 4979

email : alex@alexentertainment.co.uk

--------------------------------------------

Link to post
Share on other sites

Looks the same on my mobile;

HTC Hero with Android 1.5

Have to scroll around to see anything. I can pinch-zoom, but its just like any other website.

 

 

Rather than re-inventing the wheel, there is a CSS selector for this purpose;

<link rel="stylesheet" href="http://domain/mobile.css" type="text/css" media="handheld" />

 

You can also specify other options ie:

all

Suitable for all devices.

 

braille

Intended for braille tactile feedback devices.

 

embossed

Intended for paged braille printers.

 

handheld

Intended for handheld devices (typically small screen, limited bandwidth).

 

print

Intended for paged material and for documents viewed on screen in print preview mode. Please consult the section on paged media for information about formatting issues that are specific to paged media.

 

projection

Intended for projected presentations, for example projectors. Please consult the section on paged media for information about formatting issues that are specific to paged media.

 

screen

Intended primarily for color computer screens.

 

speech

Intended for speech synthesizers. Note: CSS2 had a similar media type called 'aural' for this purpose. See the appendix on aural style sheets for details.

 

tty

Intended for media using a fixed-pitch character grid (such as teletypes, terminals, or portable devices with limited display capabilities). Authors should not use pixel units with the "tty" media type.

 

tv

Intended for television-type devices (low resolution, color, limited-scrollability screens, sound available).

 

Source: http://www.w3.org/TR/CSS2/media.html

 

This is a much better way to do things.

 

Jason

Link to post
Share on other sites

Jason...

 

YOu're a star :)

 

I'll have a rethink on how I'm doing it tonight....

 

Cheers :)

-------------------------------------------

Web : http://www.alexentertainment.co.uk

Web : http://www.alexskaraoke.co.uk

Phone : 07525 645750 / 0800 612 4979

email : alex@alexentertainment.co.uk

--------------------------------------------

Link to post
Share on other sites

It'll probably make more problems that it solves - but if you use a good CSS layout (ie, no tables!), it should be the way to go.

Also - dump the "iPhone" idea - lots of phones have browsers, and you'll be alienating non iPhone users. Stick to "mobile" (as per Facebook etc)

 

Use background images, and you can have different sizes for each display by overriding the class in the stylesheet.

Also consider TV (ie Wii and PS3/XB360- but not sure if they have a browser..)

 

Wii is ok for 800x600 (I think).

 

The browser on my 'Droid phone is very good - handles Flash very well, I've also got the Opera Mini browser, that should report handheld (will have to check one day).

 

I assume you're going for the mini-site, rather than a mobile template for the entire site?

 

I actually doubt this is worth the effort, I sometimes surf DJU/BBC News on my mobile, but only for quick fixes.

When I was in Swanage over the weekend, I took my eeePC and used my mobile for broadband - so had a fairly ok keyboard+screen.

Actually doing anything on a mobile is still very painful. Part of the problem will be clients logging in for the first time - using an onscreen keyboard to enter their userID and password (when its normally stored on their main PC browser).

 

If you're simply setting up a front end to DJEP, then I guess this is ok. Creating a specific mobile website (unless there are other reasons - ie portfolio), really can't be worth the effort for a single DJ.

Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...