|
» Subscribe » Favorite Links » What is S60? » Freeware & Trials » S60 devices » Hints and tips » About this blog |
» Application development (24) » Applications (36) » Devices (21) » Games (7) » General (40) » Imaging (9) » Music (17) » Python (3) » Video (40) |
|
» New Mobile TV Receiver Accessory » Video Podcast Roundup to watch on Nseries » And the TIPA goes to... » Top Classic Smartphones » GPS Location Tagging Integrated into the Camera |
|
Subscribe RSS 2.0 feed |
Subscribe Atom feed If you wish to receive email notification, please here » |
|
Kevin's Jaiku Badge |
|
Carol's Jaiku Badge |
« Demoing S60 on a PC | Main | Internet radio on S60 mini-review »
Wouldn't it be nice if all those great YouTube, IFILM and you-name-it videos could be watched straight on your mobile? Today there are some technical barriers but the day will come eventually, no doubt.
We did some studies about how well S60's current applications cope with popular Internet streaming video sites. The results have been steadily improving, but are by no means satisfactory yet. Here are some issues we have identified so far, and some thoughts on how service providers could help out mobile users already today.
1) Pay attention to your HTML/JavaScript/Flash
Mobile browsers are getting better all the time with complex HTML pages, but they have limits. S60 Browser can choke on very large amounts of data or too complex JavaScript. Excess use of Flash content makes numerous sites non-usable for mobile browsers. In our results, Javascript by itself caused 36 percent of problems. Flash made up another 14 percent, bringing the total to 50 percent.
2) Use a mobile-friendly video format
Many of the most popular sites use Flash Video (like YouTube or Google Video), it's not compatible with mobiles. S60 supports MPEG-4 and RealVideo for streaming, both are widely supported by PC players also. MPEG-4 AVC is rapidly gaining popularity, not least because iPod/iTunes have embraced it for downloadable content. In our study non-supported video format caused 23 percent of problems.
3) If using embedded media player, provide alternative link
Many sites use embedded video player, which won't work in a mobile browser. The easiest way to help mobile users is to provide a direct link to the stream. A total of 11 percent of sites failed because of this "oversight".
4) The rest
The rest of failures were caused by such more obscure problems as TCP-only transport, SMIL markup and auto-forwarding.
Ok, here are the problems, what about solutions? Here are some of the things S60 is doing to improve the situation:
1) Embrace AVC video codec. Many of the S60 3rd Edition devices support AVC, and we are adding it is a standard codec during 2006.
2) Improve the browser. The new S60 browser is already included in most S60 3rd Edition devices, and it will be the only browser in the next release, Feature Pack 1. This browser shares the same rendering engine with Apple's Safari browser, we are quite confident about it.
3) Support embedded video. This will be included along with the new browser in 3rd Edition, Feature Pack 1.
What do you think about our results, have you had similar experiences? What about our actions, are we doing enough, and the right things?
Comments
This is not stictly net video related, but it's about the new S60 browser and making pages mobile friends so hopefully not too OT! :P
I was fortunate enough to play a bit with the new S60 browser at the CeBIT and I noticed that it seems to ignore CSS stylesheets directed at "handheld" media. You guys are doing a great job making the web more useful on mobiles but if this is deliberate behaviour I think it would be a great shame.
When using CSS to style and layout an (X)HTML page it is possible to specify a particular media the styling should apply to (either via the <link> tag's media attribute or using @media inside the CSS). A device should only apply the style sheet info that matches its own media type as well as any styles not directed at a particular media (in which case media="all" is implied)
For PC's the correct media type to apply is screen, for phones and PDAs strictly speaking it should be handheld. However, the new S60 browser always seems to use the screen CSS even when handheld CSS is available. (Btw, the old S60 browser gets this right!)
This means it becomes impossible for web-designers to offer an alternative page layout / design which is optimised for mobile devices which is a big shame. Granted, the new S60 browser does a very good job of displaying pages like they would on a PC, but there are still good reasons why a mobile optimised design should be preferred (when one is provided by the page designer that is):
Of course, very few pages use handheld stylesheets (most don't even bother specifying any media) so I can understand the S60 browser trying to emulate a desktop browser as best as it can. However, I think if handheld CSS is available it should not be ignored - otherwise there is even less incentive for web designers to use it. My recommendation would be: If a page does not specify any CSS media, only has screen media or a mixture of the two then that CSS should be applied (no change there then). However if some handheld CSS is available then the browser should use that (together any CSS for no specific media / all medias) but ignore CSS for any other media such as screen.
That way on 99% of sites there is no difference to the current behaviour - the browser just tries to make the best of what it's got. But on the few sites that actually specify handheld media (which would imply that the designer has deliberately designed a mobile version that he/she expects to be used) that gets used so the user always gets the best and most accessible experience.
Well that's my $0.02 anyway! Sorry this post is so long but I just had to get it off my chest in a place where Nokia developers might actually see it. Thanks for reading!!
Posted by: James | March 27, 2006 02:31 PMMakes sense to me! Comments from our OSS browser people?
Posted by: Jukka | March 27, 2006 02:40 PMHey Jukka, can't believe you wrote this blog post without referring to my Smartphones Show! 8-)
Or does it not play *directly* enough on the smartphone?
You'd probably need 3G data for 300kbps to be streamed in real time.... I'm stuck on GPRS here!!
Just for the record, for others, the Smartphones Show is MP4 (Nseries compatible) and is at http://3lib.ukonline.co.uk/sshow/
Steve Litchfield
Posted by: Steve Litchfield | March 27, 2006 04:42 PMSteve, it's in HTTP server and thus not streaming right? My post is more about streaming video, but I realized it might not be clear enough (especially since I mention Google Video etc.), sorry for the confusion!
Posted by: Jukka | March 28, 2006 10:31 AMErr... plenty of http videos stream, depending on file type. Windows Media and Quicktime/MP4 videos can all be set to stream when encoding. Certainly the Smartphones Show streams fine on the desktop. Though when I went there on the Nokia 3250, all I got was file too large 8-)
I think asking mobiles to stream 50MB videos is unrealistic anyway. 50MB on my European pay-as-you-go data tariff would cost me £350!
Steve
Posted by: Steve Litchfield | March 28, 2006 11:04 AMThat's right, but we don't support HTTP streaming.. so there is one thing to add to our list :)
WLAN is hopefully disrupting things also.
Posted by: Jukka | March 28, 2006 11:14 AMSeries 60 devices only stream from RTSP by default. To stream via other protocols you have to provide your own solution
:-)
Don't know about UIQ!
Boom
Posted by: akboom | March 28, 2006 11:24 AMgreat info Jukka ! Thanks.
Speaking of Flash Video format you can use some server tools to automatically encode Flash video into 3gp and stream them via RTSP :)We used this solution for a project and it works great !
Flash Lite player currently does not allow you to play a flv file but you can do it using the 3gp format.
For what concern the data I totally agree with Steve : you need a 3G connection !
Posted by: Marco Casario | April 1, 2006 12:36 AMif you want to do this, you should use record internet radio tool first!
Posted by: suangsang | August 1, 2006 07:09 AMSorry suangsang, I didn't get that?
Posted by: Jukka | August 1, 2006 03:03 PMto Jukka, what do you mean? i can't understand!
Posted by: suangsang | August 2, 2006 11:53 AMthts great
Posted by: shital jethva | August 7, 2007 12:10 PMNokia announced a new mobile internet video experience which enables enhanced internet video consumption by bringing You Tube videos into the hands of Nokia
Posted by: offshore software development | September 17, 2007 10:36 AMI came across Jame's post because I am trying to use a media stylesheet of the handheld variety for a website i am building. I just tested it on N95 and was quite honestly stunned to see that the N95 browser did not seem to detect the handheld stylesheet at all. Media stylesheets are a great idea, and seem to be a W3C standards things, so, I find that very odd to hear that S60 browsers do not support it.
A lot can be done with stylesheets to make a "standard" website much easier to navigate on mobile. So why are handheld media stylesheets seemingly not supported? :(
Posted by: tim cole | November 11, 2007 06:48 PMI came across Jame's post because I am trying to use a media stylesheet of the handheld variety for a website i am building. I just tested it on N95 and was quite honestly stunned to see that the N95 browser did not seem to detect the handheld stylesheet at all. Media stylesheets are a great idea, and seem to be a W3C standards things, so, I find that very odd to hear that S60 browsers do not support it.
A lot can be done with stylesheets to make a "standard" website much easier to navigate on mobile. So why are handheld media stylesheets seemingly not supported? :(
Posted by: tim cole | November 11, 2007 06:49 PM