My stance on web vs app

Ok so many of you I wont mention names *cough, cough Bill have been asking about building another app and wanted to know my stance. Well here it is:

A company needs to have a mobile web website. While the percentage of traffic striking the site via mobile is fairly little now all of the clients I have spoken to have actually seen the traffic increase substantially year over year and in some cases month over month. The other thing to comprehend is why are they hitting your website via mobile?

That being stated it may sound like I am promoting against mobile apps which, I am not. Apps are a really effective mobile engagement mechanic and having your app found on the most personal thing a person has is a big benefit.

All that being stated I think the largest problem with whether to go app verse mobile web is more based on cost and the functionality which is required for the app. The major issue with app development is the cash you will certainly need to pour into a minimum of 2 operating systems (iOS and Android) for reach and need to resolve users of Blackberry, WP7 and function phone which do make up a smaller portion however still substantial reach amongst customers.

If the content and performance for the app is fairly easy and which does not require to utilize many facets of the “native” functions of the phone OS, I would recommend construct using HTML5 (mobile internet). As soon as for all platforms and conserving an entire lot of cash doing it, for the most part you are constructing it. One construct, which can be made use of for your mobile site too, and can be accessed with a much better user experience across almost all mobile gadgets.

Now right here is the kicker. In the consumer space everything is about the “app” and getting that priceless little icon on somebody’s phone is a really powerful thing. If you go directly mobile internet, in the minds of a lot of consumers, you do not have an “app” therefore you seem to be behind the times and if your competitors does you run a strong danger of losing that consumer long term.

To relieve this issue and the customer’s big desire for apps, I would recommend developing some easy “native wrappers” for all the significant mobile OS’s. Wrappers are really low-cost produce and basically are a means you can “deceive” the consumer into believing they have an app. This could be as easy as an “app” that launches the browser, conceals the address box etc and calls the HTML5 you have actually currently produced. The consumer has the ability to download the app from an app establishment, position the icon on their mobile property and use it to their hearts material. From a company point of view you get the very best of all worlds, considerably lower development costs, one central content management system and the halo result of having an app in the market.

I wish to discuss this does not work in all cases. Then there might not be any choice however to go with a native application, if your app requires more intricate performance and making use of HTML5 affects the user experience.

No matter how you slice it mobile is hear and business have to move quickly to grab their area. All of this feels so much like the web boom we saw in the late nineties as companies tried to determine how to deal with this new thing called the internet. Those who moved early and thoroughly prospered those who did not lost. I would offer examples however that was for life ago in tech time, I mean 10 years? Maybe if I can discover my Palm Pilot I can inform you, I think had it written down there.

How to add an image to html

uhhm posted this for those who are working on the Baker project. I know that we are all tired and we tried to develop the best people but C’mon you don’t know how to add an image tag?

Its just insane get it together team. Here it is: <img src=“smiley.gif” alt=“Smiley face” height=“42″ width=“42″>

Oh and for future reference please it up http://www.w3schools.com/ for all the html your heart desires.