BCRose
Nuke Master Posts:131
|
08/26/2010 8:11 PM |
|
So has anyone made a site for mobile devices? What are the challenges? I want to redirect smart phone users to an alternate site compatible with these devices.
Any suggestions, where begin?
|
|
|
|
|
Joseph Craig DNN MVP Posts:11667
|
08/26/2010 9:11 PM |
|
There is a lot of conversation going on these days regarding mobile devices and DotNetNuke. If you Google "Hackathon" you will see discussion of an event conducted last and this week with the aim of producing mobile apps that consume information from DotNetNuke sites.
You'll also find mobile skins.
|
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|
BCRose
Nuke Master Posts:131
|
08/26/2010 9:34 PM |
|
Thanks Joe, interesting stuff. Also looked for mobile skins on Snowcovered and found a few. Seems like it is only a matter of time. |
|
|
|
|
SixfootStudio
Nuke Ace Posts:47
|
08/27/2010 10:02 AM |
|
Hi Joseph and BCRose, We need to implement a mobile site for our client already using DNN and I wanted to know where I would begin with this? I know that creating the skin is not the problem, but the problem comes in when you need to know what device is hitting your site and what skin to deliver from there. I don't know anything about WURFL etc, and wanted to know if this is something that needs to be looked into? I have seen one company who sell their modules to convert the site to a mobile phone, but we need to do this from scratch. Many thanks. |
|
|
|
|
Joseph Craig DNN MVP Posts:11667
|
08/27/2010 6:41 PM |
|
One good place to start might be this set of tutorials: How
to Create an iPhone App with OWS. This is a really good place to start, as it deals with a number of issues related to showing your site in a mobile browser. While this is an application of the OWS module, I would point out that you don't need to use OWS. In this tutorial, Paul uses Request.UserAgent to identify the browswer. You can detect iPhone and any other browser if you look at that attribute of request. And, you can use it to load conditional CSS, to do redirect, etc. There are some "skin switcher" modules floating around that will load a skin based on the browser, or on other actions. If you look at the Minimal Extropy skin and Lee's recent skinning tutorials, you'll see how to load CSS depending on the browser. |
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|
BCRose
Nuke Master Posts:131
|
08/27/2010 9:54 PM |
|
I see some for sale over on Snowcovered. Reasonable price. |
|
|
|
|
BCRose
Nuke Master Posts:131
|
08/27/2010 9:57 PM |
|
Posted By SixfootStudio on 27 Aug 2010 10:02 AM Hi Joseph and BCRose, We need to implement a mobile site for our client already using DNN and I wanted to know where I would begin with this? I know that creating the skin is not the problem, but the problem comes in when you need to know what device is hitting your site and what skin to deliver from there. I don't know anything about WURFL etc, and wanted to know if this is something that needs to be looked into? I have seen one company who sell their modules to convert the site to a mobile phone, but we need to do this from scratch. Many thanks.
This seems like the answer for you
http://www.snowcovered.com/Snowcove...geID=18558 |
|
|
|
|
Joseph Craig DNN MVP Posts:11667
|
|
sarendt
Nuke Newbie Posts:7
|
11/09/2010 9:46 AM |
|
We're exploring how to create mobile versions of DNN sites as well. Where we're coming up short is in finding a module that allows the override of the mobile site, ie "tap to view entire site." We'd like users to be able to view the entire site if they're looking for specific content that isn't necessarily offered in the mobile view. Any suggestions on modules that offer this functionality, or a workaround for it? |
|
|
|
|
Joseph Craig DNN MVP Posts:11667
|
11/10/2010 6:40 AM |
|
Possibly you could have two URLs for the site and load skins depending
on the URL. I haven't tried that, so I don't know if it will work.
|
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|
bill
Nuke Active Member Posts:25
|
11/17/2010 10:45 AM |
|
We're starting down the mobile skin road too.
SEO implications using multiple URLS?
Bill |
|
|
|
|
Joseph Craig DNN MVP Posts:11667
|
11/18/2010 7:24 AM |
|
Yes, they count as different sites as near as I can tell.
|
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|
SixfootStudio
Nuke Ace Posts:47
|
11/23/2010 6:48 AM |
|
This subject is hotting up and I am glad to see it. This is a post I left on the DNN forums but man I get a lot more success out of these forums! I have managed to dig up some more information on a company who recently did some work on DNN Mobile sites. Here you can find Beatriz Oliveira having a talk about DNN Mobile at Bind: http://www.bind.pt/NewHome/tabid/29...fault.aspx You can download the Blueprint Skin, MobileCSSInjector and the Powerpoint presentation she held at the time. |
|
|
|
|
Joseph Craig DNN MVP Posts:11667
|
11/23/2010 7:28 AM |
|
Beatriz Oliviera also spoke at the recent DotNetNuke Connections event. I believe that some of those sessions were recorded and that they will be available fairly soon on the DotNetNuke.com website.
|
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|
Web Services
Nuke Master Posts:322
|
06/08/2011 2:25 PM |
|
Here's what I've learned from my research and experiences. Your SEO will be affected, but it shouldn't be too bad, as long as you designed your original site with best practices. You can add a css file called handheld.css that most phones will recognize and it will trump any other css files. This isn't a standard, however, and the iPhone doesn't recognize it, just every other mobile brower (go figure). Anywho, the easiest way to do this is to buy a module that will select a proper skin based on what browser is hitting. Mobinuke is pretty good at this for a relatively cheap price. A few things to keep in mind when you develop a mobile skin. 1. KEEP IT SIMPLE. Most of the time when someone is looking at your site via a phone, they are not "browsing" they are looking for something specific. This is generally an address, phone number, directions, email, or pricing. Try to keep your most pertinent and most viewed content on the first page. 2. Through my experience I found that having a back link is good, as not all phones have the inherent "back" button that browsers do. 3. Keep as many pictures off of your site as possible. These may make it look pretty, but they require bandwidth and on a phone, that's still a big deal. 4. Have a link to allow them to go to the full site if they wish. Some phones handle full sites as well as they handle mobile sites, like my droid |
|
|
|
|