Hello to everyone in the “Building Mobile Web Applications Using HTML5 & CSS3” 5 Week Training Course, hosted by American Honda Motors.
I’m going to try to respond to all the comments as soon as I have a chance to read through them all. Thank you to everyone who attended this evening -especially those who participated in the class discussions; I hope it wasn’t too boring for too long. Oh, and fwaiy, I’m going to try to get Red Bull to sponsor us some wings.
Here is the link to the SpriteMe site we tried (SUPERFAIL) visiting during class: http://spriteme.org
A special thanks and Agile shout-out to my modest, humble friend and former DIMG colleague Jakob — his commute makes everyone else look like a 90 lb weakling. Thanks Jakob for reminding me about Google Page Speed Insights.
Jakob is a world-class front-end developer and it is to our collective benefit that he has attended the past two sessions.
5 thoughts on “For Everyone Attending the “Building Mobile Web Applications Using HTML5 & CSS3” 5 Week Training Course”
Sorry about that!
I’ve turned on user registration, so you ought to be able to leave comments now.
Also I was wondering about data security. Do native apps have any security benefits over web apps for mobile? Should I assume security considerations for mobile web apps are the same as for desktop web apps? Are there any particular security concerns specific to mobile web? On a quick google search I found the following:
would you point to any additional resources for info?
This is an interesting question. It really begs us to ask, “if a handheld device is itself insecure, what does it matter?”
Let’s consider one of the best kept secrets in the world: the secret formula for Coca-Cola. If Coca-Cola were to put that formula on a iPhone, would it matter if it were stored in a native (installed) app? If the phone was lost or stolen, would it matter if it were stored encrypted in Safari mobile?
I believe the answer to this is no. It takes a small amount of expertise to access “secure” data stored on lost iPhones. The web has numerous sources for information on how to perform such operations.
As for network integrity, installed/native apps are far less vulnerable to network attack on the client side, but most of those software manufacturers still have trouble with security — its simply not on the phone itself.
In short, storing information on an iPhone protects the data on the phone itself, but only causes intruders to look for vulnerabilities elsewhere in the network topology.
re: Responsive design, are there best practices for organizing content (for technical efficiency and design flexibility)? (i.e. how to plan content that may be viewed on desktops, tablets, phones). URL’s are fine.
I will leave that to Joe to discuss when we get to responsive design. My personal opinion is that one of the core concepts would be this: in writing CSS definitions, use percentages instead of pixel values.