I have PHP-MySQL dynamic corporate website. All text and image based content is managed from admin panel. Desktop version website is displaying very fine in mobile phones too. Layout is also fine and structured.
Now I want to create mobile version of this website but I am novice in this field. I have read few topics on this website about mobile version of website but I have found no answers I am looking for. I have also read about responsive website solution.
Please guide me with some helpful info so I can go in right way.
Q 1. If I use responsive website technique, then same website and it's layout will be used for desktop as well as different screen resolution mobile phones? Please reply.
If an answer of above question is 'YES' then please reply for below.
Q 2: Will I need to redesign my existing desktop version website using responsive webdesign technique so it can work in all screen resolutions devices? Please reply.
If an answer of above question is 'NO' then please reply for below.
Q 3. My current desktop website content is managed from admin panel. So if I host mobile version website on sub domain (like m.sitename.com) then will I able to use same content for both main domain as well as sub domain where mobile version website is hosted? Please reply.
Q 4: Is it compulsory to use any tool like http://www.mobify.com/ to design mobile version website? or can I design it in same way as I am doing for my desktop version website? Please reply.
Thank you in advance,
First to answer your questions:
Q1: Yes, if you're using responsive web design you can use the same layout for all kinds of devices.
Q2: Depends on your project, but you'll probably need to rewrite some parts of your layout to make it more responsive.
Q3: Yes, if your code base is somewhat reusable this should be very easy.
Q4: Nope, you don't need any extra tools. You could write everything yourself.
Depending on how complex your front-end stuff is, I'd recommend to use a fronend framework like Bootstrap, Foundation or INSERT_ANOTHER_MOBILE_FRIENDLY_FRONTEND_FRAMEWORK_HERE. These frameworks make it very easy to write responsive websites.
Related
I'm trying to create a mobile version of an already existing website. I've tried to read the previous questions on SO but they don't entirely give me all the answers I'm looking for.
The options I have to make my site more mobile friendly are:
1) Convert my current website to be more responsive using CSS Media Queries:
I don't think this approach is suitable in my case, as the UI is fairly complicated and there is more information that I can properly show on a mobile. I will need to make sure I don't show some information that is not as relavent on the mobile.
2) Use php detection and serve up different versions of the same page by using different templates:
This way I can show only what is most useful on the mobile version and load up additional css which specific to mobile. A lot of websites including StackOverflow/Imdb seem to be going this route.
If i go this route, Is it necessary to have a subdomain such as m.mywebsite.com and serve a mobile version on that? Or can i just serve the current page with the same domain and url structure to mobile, only different html/css to better suit mobile. I would prefer to not have the subdomain(StackOverlow seems to be doing this). Also will this be confusing to users and something to avoid as a best practice? Most importantly, how will this affect the SEO for the site? Since some content is missing on the mobile, but present on the desktop, with the same url structure - will it trigger a red flag in search engines and penalize?
Thank you!
Regarding option 2:
There's no need to do the m.domain.com subdomain thing anymore. It makes life much more confusing.
I use the mobiledetect php library (there's a wordpress plugin for it too) to determine the client.
Then use conditionals in your php to provide different content for each.
Regarding indexing, the crawlers will not be flagged by mobiledetect as mobile browsers, so they will index your desktop version of the site. You want this, as the desktop version will no doubt have more content and provide increased page rank. The crawlers will never know that mobile-only content exists so there won't be any penalty.
I want to build a mobile site on wordpress.
What Im looking to do is detect if its being loaded on a mobile device and then switch themes based on this.
Usually I implement a redirect to a mobile m.mysite.com address when using different platforms, but is there a more efficient way of doing this on wordpress, where I can keep the address but have it load a different theme?
Im not keen on doing a responsive site as I want to completely restructure the layout.
Thank you
This links will help you. Try it.
http://wordpress.org/plugins/any-mobile-theme-switcher/
http://wordpress.org/plugins/mobile-theme-switch/
http://wordpress.org/plugins/mobile-theme-switcher/
You are probably looking for the Auto Mobile Theme Switcher plugin.
Another option may be to add a WordPress Mobile Theme that creates a mobile optimized RESS (Responsive Server Sided) layer to your site - both WPTouch and JumpMobi offer this type of functionality you are looking for straight out of the box.
HTH
My question is about resolutions and user interface of web sites. I am developing a free web site for a non profit organisation for having experience and I have not worked with mobile apps/ web sites. Will thankful if you please can help me.
Can you please guide me as per best practices UI for computer browser and for mobile are same or two different UI are developed ?
I am also confused what is standard resolution for a web site and how to manage resolutions on different screen sizes (of course cannot develop for different screen sizes).
Please guide.
Thanks
A common technique in use right now is responsive design. That is, your design and layout of the page will adapt for the resolution and orientation of the device it is being displayed on, without a need to change anything.
The easiest way to get started with this is CSS media queries. Check out this article for more general information: http://kyleschaeffer.com/best-practices/responsive-layouts-using-css-media-queries/
I have a site made by dnn6.i need to add the mobile version of the site.how can i solve this problem.or is it possible to convert mobile compatible site.
There are several ways to accomplish this. You need to evaluate each and determine the best route the most closely matches your goals and amount of administration that you are comfortable with. Another thing to keep in mind is the user experience you end up delivering to your visitors.
Probably the most flexible solution is to use responsive web design to adjust and change the content and layout according to the dimensions of the device that is currently viewing the site - regardless of the kind of device we're speaking about. American Athlete Magazine is a great showcase for this approach.
You can also have a mobile section on your main site, or another site altogether that displays content optimized for mobile viewing. In this scenario, you would create a mobile friendly design that offers the best user experience for mobile visitors, as well as maintain content in a way that is equally friendly. Then, redirect visitors to the mobile site or mobile section of your site using the built-in redirect tools. They are in all editions of DNN as of v06.01.05. An example of this method can be seen with Day of DotNetNuke and its mobile variant.
There are of course other ways to proceed, but these are the most common. In either scenario you can use content sharing to make maintaining content easier, but you really should balance ease of administration with the expected user experience of your visitors.
There is a lot more information about the mobile capabilities in the DotNetNuke Wiki.
There are different approaches like Will stated above.
You can create a child portal (yourdomain.com/mobi or mobi.yourdomain.com) and modify an already existing skin (check out codeplex for MIT license mobile skins: http://dotnetnuke.codeplex.com/site/search?query=mobile%20skin) You'll need to put in a redirect in so when a small display pulls up the site it takes the user to the mobile version. The problem with a child portal is that you will have to maintain two separate versions... so if you plan to make many changes, consider option 2.
You could also upload the mobile version of the skin to the root portal, but you'll need to make a skin adjustments as you'll want the mobile skin to pull up a dynamic menu. If you choose this path, you can use the same instances of modules on separate pages (so you only have to make changes once and it will replicate on the desktop skin and the mobile skin).
You can wait a little while... DNN 6.2 is going to be released with mobile redirect capabilities (currently only found in DNN Pro and Enterprise). I'm not sure if DNN is releasing a mobile skin with the new version.
If you need help, I'm happy to bill you for the right solution :) ack !!
I am building a website both mobile and pc version.But I am in a fix what should be used to do it.I have some question for which I am confused :
1. make a website with separate mobile version and pc version and render page depending on the device users use ?
2. Another is a single version website that would be all device compatible.this can adapt the layout according to the device resolution ?
3. if I do the thing I mentioned at point 1 , Can I built a site with wordpress and mobile version with jquery mobile ?
4. If I use a mobile compatible wordpress template I mentioned in point 2, can I use all other plugin form outside?
Please Help me.Thanks in advance.
So what should I do? building two different version ?? if yes, Can I
use the wordpress for both? do you know any plugin or way to make both
pc and mobile version in wordpress ?
This is what I did to achieve what you are aiming for:
Install WordPress as normal.
Add the Mobile Smart plugin - or possibly mobile smart pro.
Create a theme for regular desktop browsers and activate it in WordPress
Create a completely separate theme for mobile browsers. You may wish to use the sample code supplied with the plugin; I created my own from scratch.
Change the settings of Mobile Smart so that it knows which is your mobile theme
Add content and enjoy!
Please read the documentation with Mobile Smart. It is important to understand what it is doing.
Also, remember that your two themes are completely separate, in completely separate directories, so you can use completely different functions.php, headers, footers, scripts, etc. as necessary.
Quote from https://github.com/ChristianPeters/crispy-mobile that I agree with:
CSS media queries are nice. But not for mobile.
They just add up code you send to your clients instead of reducing it for mobile devices.
Imagine you want to make a responsive product page.
Do you really want to deliver a big 90KB product photo, if a 15KB photo would already fill the mobile screen?
Do you really want to compute personalized product recommendations if they are just hidden afterwards?
Do you really want mobile devices to download and interpret your whole stylesheet if half of the interface elements are going to be hidden anyway?
You don't.
If you start mobile-first, don't let your mobile performance be affected by additional desktop features.
Be kind, serve the clients exactly what they need.
If the mobile internet was fast enough and limits weren't as low as they are, I would probably think the other way. But we have to wait few years for that. For now in my opinion it is better to build seperate mobile website. But it is also very useful to have responsive design - that can't hurt even with separate mobile design.
I'm going to avoid too much subjectivity here, as everyone will have a different opinion.
Yes, I have this approach working well on my company website (www.achaleon.com). I was involved in the beta testing for a WordPress plugin called Mobile Smart Pro. It implements elements from a bigger open source project to detect mobile devices and apply a completely different theme to the mobile site. It has the advantage that you can create two completely separate themes and optimise every aspect of them for the device and the context in which it is being used. You can even serve up different content if you wish in the two versions.
This approach requires careful planning and thorough testing. It is also more demanding for the designer. I have friends in the WP community who have built sites this way. My understanding is that this requires stronger programming skills (you need to plan far more carefully than with a standard 'static' css implementation). They used cssgrid.net as a start point