Author |
Message |
neralex
Site Admin

Joined: Aug 22, 2007
Posts: 1775
|
Posted:
Thu Dec 22, 2011 6:14 am |
|
|
|
 |
montego
Site Admin

Joined: Aug 29, 2004
Posts: 9457
Location: Arizona
|
Posted:
Thu Dec 22, 2011 8:04 am |
|
Looks really nice.
<caution>
The more and more I work with mobile devices, the more cautious I am about thickening up my sites. We have really gone almost full circle back to the days of dial-up access for our PCs where we had to worry about the size of our site data coming back. Some are slowly getting 4G, but it is going to be slow in coming for the masses, just like broadband did.
So, while all these new JavaScript based "treats" look fantastic and provide more of a native application type feel, one needs to be cautious to not just create eye-candy, but make sure what they are creating is going to be helpful/useful to your target audience.
</caution> |
_________________ Only registered users can see links on this board! Get registered or login!
Only registered users can see links on this board! Get registered or login! |
|
|
 |
Guardian2003
Site Admin

Joined: Aug 28, 2003
Posts: 6799
Location: Ha Noi, Viet Nam
|
Posted:
Thu Dec 22, 2011 10:19 am |
|
Absolutely, I know the iPhone has a maximum limit on the size of JS files it can use so I think it's safe to say other mobile OS would have the same or similar restrictions. If your aiming at the mobile sector, you definitely need to be using HTML5 to get you on the right track for future-proofing. |
|
|
|
 |
spasticdonkey
RavenNuke(tm) Development Team

Joined: Dec 02, 2006
Posts: 1693
Location: Texas, USA
|
Posted:
Thu Dec 22, 2011 1:12 pm |
|
neralex, nice script. nothing worse IMO than those standard select, radio, and checkboxes on a dark colored theme.
In regards to mobile friendly sites, that is an issue that has become increasingly complex.
http://www.slideshare.net/bryanrieger/rethinking-the-mobile-web-by-yiibu
The idea that seems to make the most sense is "progressive enhancement" where you deliver a simple mobile friendly site to all users, and enhance it based on the capabilities of a given device; based either on the user-agent or display-width. This gets complicated with the variety of devices, and is even more complex if you want to selectively load JS resources based on a specific device.
For me personally I don't want to handcuff my site(s) from using features that won't work properly on a mobile devices... That would mean no jquery animations, custom fonts, etc.. I think the most practical approach (for me) within the context of RN, would be a separate mobile friendly version of the site... But every site is different, if I was working on a site that catered to a mobile audience I would probably use "progressive enhancement" as above; and shy away from too much JS.. |
|
|
|
 |
montego

|
Posted:
Fri Dec 23, 2011 10:00 am |
|
Actually, I believe we can no longer separate the two - mobile vs. not. Mobile access to our sites is becoming far more common than you might think, especially (but absolutely not limited to) in parts of the world where there is no traditional broadband access, or any access altogether. In these areas, the internet is being "served" via mobile devices - even land-line infrastructure build-out is being surpassed by wireless communications and, thus, mobile devices.
I, too, am struggling with the direction of RN and mobile. One side of me wants to make my sites one-size-fits-all, using some tricks, good structure, good CSS and multiple style sheets and the other side wants to just be able to check the viewport size and redirect to an "m." version of RN. I just can't decide which way to go. Might be worth a specific forum thread... I'll have to look for one already and if not there, create one. |
|
|
|
 |
|