ss's Original Blog
Google wrote me a warning letter about 2 weeks ago asking me to make my website more mobile friendly. Google said the increase demand in mobile phone browsing had been tremendous. Well, it is not a warning for doing something that pissed google off. It was actually a concerned notification. Google anticipated that the wave of mobile surfers will get stronger with the passage of time and webmasters were advised to cater to their needs. If I were to take it as a friendly notice I don’t need to do anything. I choose to take it as a stern warning so that I will have to adapt before I get left out.
Heck! I don't have the slightest clue where to start. I hope I could just wave a magic wand with some code and bingo! Fortunately, google is a good place to start looking for those hocus pocus code. Knowing the right keyword to punch into google would help. Next comes the endless list of reading materials on the technology to make your website flexible to multiple devices. Climbing the steep learning curve was no fun. It’s just nothing but reading without having enough knowledge to start doing something.
I concluded that it was about starting small. Fit the small screen then the bigger ones and eventually the desktop. This calls for a re-engineering as my website was catered for desktop size. I have started with reducing the size of my menu. I used single word titles for the menu items to shorten it for mobile size. Sub menu items could use double or triple word titles. Whoopee, I managed nail down some of the problem. For screen smaller than 320 pixels wide, I may have to do away with the menu. I will get around to this but the next step would be resizing all my images. I am going to do a lot of experimenting to find a good size that could be stretch or shrunk to fit across the platform without losing too much picture quality.
My Comments
I was having problems figuring out the method to build a flexible website to fit all devices. Perhaps you should consider writing a website on 36btips to building a webpage.
No comments:
Post a Comment