Skip to main content

Google Gears up for HTML5

I am not that big fan of Google, (ok I am lying, who isn't a fan of Google?) But you like them or No, one thing you must agree, they are technology savvy and not money-power hungry, good for poor developers like me.

Google always came up with something new to surprise us and even if they did not intend to surprise us, we do get surprised with their announcements.
Devta
Google has announced that is it dumping Google Gears for HTML 5, which is a surprise yet a technically sound move.

With Google Gears, they had to build it compatible around every browser which was a headache for Google but if they do have the same technology around HTML 5, then I every browser compatible with HTML 5 will have offline access to Google products.

ReadWriteWeb says, "We question whether offline access is even necessary. After all... in today's world, you're never too far from an internet connection. We concluded that offline access is important now, but less important with each passing day." more here.

However, this sentence may be true for US and UK, but really the world is more than just that, infact most of the Google products are used in India (where I belong) that other countries. There are many places where offline access is necessary. When I was consulting a client on Salesforce, his major requirement was that the sales rep travel to the part of the world which has limited internet access. A company dealing with metric TONs of iron ore may not exactly use internet or has time to study internet. They use their MIS system is enought for them presently. So ReadWriteWeb, if you are listening, the world is very large and the internet is not yet wide spread around the world, and we do need offline access.

So, moving over Google Gears, I am enjoying Google Wave with Elizabot, for those who do not know her, a new post is coming up soon.

Till then wait for the next update.

Cheers,
Ravan

Comments

Popular posts from this blog

Video: Top ten tips on how not to ruin Salesforce implementation

Another presentation for the London Salesforce Developer Group using mobile app. 
When it comes to Salesforce development, we all know what it takes to deliver stuff. Having a certified professional helps you gain a knowledgeable partner but what about the things such as common sense?  We all know how to deliver things on client requirements but what about things that are not mentioned by the client. We will be discussing in details things that will enhance the user experience, focus on tips to read your customers mind and have a bit of perspective on the user experience.

Cache me if you can: What you should know before daring to set URL parameter on visualforce

If someone gave me a pence for every time there was an SOQL query in an APEX Class without using Limit or a condition during a code review, I could afford a Lamborgini this month. Sigh. If only. We make it a habit of going digging for data, at the very moment we need it. The crux of this problem happens when you have chain classes which are independent of each other. Each class needs the reference from a single record and we have to query for that record every single time.

While we don't see it, every SOQL query has a cost to it, and it does not go in my Lamborghini fund, however, it should. In a recent project, we had to construct an Account 360 page that could fetch information from different integration points. The page was also called using a live telephony integration, which could pass the phone number for the account. This required an ability to keep in context the Account that was on call.

Passing the Account id in URL parameter was a valid option, however, any manipulatio…

Four secrets to improve the usability of your visualforce/Lightning pages on Salesforce

In the immortal words of a certain machine returning back in time, I am back. For now. After procrastinating for over a year and drafting a lot of rants- I am back with a very important coding lesson for you. For now.

When we are designing a Visualforce page or an app or a lightning component (added that only to trick google) or any web page for that matter, we often tend to wrap up things quickly. Ask anyone on the team, how to design a good User Experience? and the person will immediately throw buzz words like Bootstrap, angular and other useless libraries (did someone squint?)

Ok, Bootstrap, Angular-Js, and all the libraries are really cool and are useful in designing a fabulous UI. They are helpful in creating responsive pages that will work on all the devices but this post is not about those. Nope. For the purpose of this post, all the external libraries and buzzwords you use to decorate your resume are useless. (Adding Angular JS in your resume for a Salesforce consultant posit…