Forum

Hi Aderson,

Thankyou for the modified skin. It now displays sub-menus, but unfortunately it doesn't display sub-sub-menus.
Also, if I were to be pernickety, the sub-menu items are different shapes.

But instead of having to do some major work to correct an existing skin, is it not possible to report the issue?
Are you able to recommend any other mobile skins, it would be nice to have a few to select from.

Also, I checked some of the responsive/adaptive skins  in the 'great skins' section of the home page of www.dnnhero.com. These look great on the latest versions of I.E. and Google Chrome, but either display badly or don't work in older browser versions (IE.8 for example). Presumably that's because the adaptive skins are using html5/css3 which older browsers can't interpret.

So I'm wondering what the strategy should be:

1) Have separate skins for mobile and desktop, use the desktop skin for tablets.
This means you'd need to maintain 2 sites effectively but at least everything would work as intended.

OR

2) Use an adaptive skin, this would cater for the latest desktop/tablet browsers and mobile browsers with just one site.
But what could you do to cater for older browsers? I can only think that you'd need a separate site, does the dnn device redirection cater for this?
Again this means the cost and inconvenience of having two sites.

I only started looking at mobile sites in the last few days, are my deductions correct or are there any better solutions?

Steve

Hi Steve,

In regards to the StoneCold skin:

1 - It was not build to have subnavigation at all. I have added 2nd level navigation on my own. There is no 3rd level navigation handling;

2 - For you to think: Your mobile site should be MUCH simpler than your full desktop site. Can you imagine people going through 3 levels of menu navigation on a mobile device. It is not very user friendly. So you should try to simplify the mobile version;

In regards to the right approach for mobile, I hate to say that, but "it depends" of a lot of factors like :

- your budget;

- how much content the site has;

- how frequently is the site updated;

Here are my thoughts in general about this:

1 - Responsive skin is nice but it my not look that nice on older browsers - even though this will be less and less of a problem;

2 - If the site's content is quite static, I would choose a mobile skin and then have duplicated content to manage, one for mobile and one for desktop;

3 - If the site's content is too dynamic with daily updates I would try a responsive option;

Those are my thoughts. I will be interviewing a great designer/skinner this week and I will be publishing his interview next week. We will be pretty much talking just about mobile development and the choices we have. This should be interesting for you to watch once it's live.

Cheers,

Aderson

Hi Dave/Aderson,

Regarding browser market, It's a good point Dave, but I assume it's not just older IE browser versions that don't support CSS3.

Regarding levels of navigation, If possible I would like to be able to cater for any request a customer might make.
Looking at demo of one of the other adaptive skins on dnnhero.com
http://www.dnnskin.net/social-silver/...
It shows 3 levels for a mobile device, I think it's quite a good the way it's displayed. Though I take Aderson's point about simplifying the site.

One thing that did occur to me, is that it's possible to 'add an existing module' from the host menu. So if you go down the separate site root, you can use the same module instances, the contents will be synchronised but the modules can be arranged differently.

Another advantage the responsive skin has is that you don't have the $360.00 per year per site cost for the device detection license, assuming you're using the community edition that is.

I look forward to seeing the interview with the skin designer when it's published.

Maybe some videos on making a site responsive would be a good idea.

Best Regards,

Steve