You can also find me on: google+, twitter,, github, librarything, granular, steam
@AnuragBhandari twitter updates
Tech enthusiast, open source evangelist, book worm, software developer, sports fan, passionate gamer, movie buff.

Mobile App Development: Lessons Learned

  1. Sencha Touch is a great framework, but requires a LOT getting used to. The officials Docs do not always have the answer you’re looking for. ST forums and stackoverflow are excellent resources to consult when in need.
  2. If you are a web developer, DO NOT waste time learning Objective-C or Java for creating native iOS and Android apps. Instead use something like ST to develop a mobile web app, and then convert it into a native app using Cordova / PhoneGap.
  3. Cordova is the renamed, open-source version of PhoneGap.
  4. If your app is data-centeric, most probably it will depend on a webservice / API. If the API and the app are hosted on the same server, no problemo. In case of native apps, that are basically web apps PhoneGapped into native apps, that’d mean calling a remote API, and that is the problem. See same origin policy.
  5. Most googled solutions will point to making the service JSONP supported; but JSONP works only for GET requests. CORS is a recent W3C standard that supports all HTTP methods, but it still doesn’t work for PhoneGapped apps. ASP.NET Web API provides an easy CORS implementation.
  6. The perfect solution is to keep making Ajax calls normally, but using the full URL of the remote API. That will work because a PhoneGapped app doesn’t render in a browser but in a WebView (through a file:// URL). So it’s not restricted by browser’s same origin policy.
  7. ASP.NET MVC 5 and Web API are awesome!
  8. You may frequently encounter annoying cache issues with PhoneGapped apps. Just place a super.clearCache() in your Android app’s main activity’s onCreate().
  9. Here’s how to create an animated splash screen in Android (though I have yet to figure out how to correctly use this in a ST-PhoneGapped app).
  10. If your device has Android 4.4+, you can remote debug your WebView-based Android apps using Chrome.
  11. JavaScript is yummy!

Sencha Touch: Third-party plugins and build errors

Nothing beats Sencha Touch when it comes to sheer number of options and versatility in developing for the mobile. ST has truly set the benchmark of mobile development done right with each major release. It has a vibrant user community, and a robust enterprise adoption. But, sadly, although the documentation is good, it sometimes feels a bit incomplete. If it weren’t for stackoverflow and ST’s official forums, it would have been difficult for me to complete some aspects of my recent mobile app project. Coming to the point…

ST recently announced the much awaited grid feature . They call it Touch Grid. On the surface, it looks super-customizable (just like everything else ST) and enterprise-ready. In short, it’s just what everyone was waiting for. Unfortunately, it is not available for free. Touch Grid comes as part of the Sencha Touch Bundle, something only suited to the enterprise due to its staggering $695 cost.

A couple of months ago, I was looking for something like Touch Grid for my app. The exorbitant pricing of ST Bundle compelled me to look for free alternatives. That was when I found Ext.ux.touch.grid. Its last release was well over a year ago now, and was tested with ST 2.2. But it still works with ST 2.3 (the current release). Including its source folder “Ext.ux.touch.grid” in the root of my ST app and adding a reference to it in my app.js was all that was needed to get it to work.

When I built my app for production deployment (sencha app build production), I got this error:

Unknown definition for dependency: Ext.ux.touch.grid

The above error basically pops up because of not adding a dependency (say, a plugin) in your ST app’s classpath. Adding it to the classpath resulted in the yet another error:

com.sencha.exceptions.ExBuild: java.lang.IllegalArgumentException

A small tweak fixed this error: I created a new folder “plugins” in the root of my app and moved the “Ext.ux.touch.grid” folder into it. I edited my app.js to change the plugin’s path, and likewise changed the classpath.

Add this to the top of app.js (before Ext.application declaration):

    enabled: true,
    paths: {
        'Ext.ux.touch.grid': './plugins/Ext.ux.touch.grid'

And add the “plugins” folder to the app’s classpath (edit .sencha/app/sencha.cfg):


Now build again, and all should be fine!
Happy coding.

MonoDevelop 4: CSS files not loading for an ASP.NET MVC4 site

MonoDevelop 4

MonoDevelop 4

If you are like me — always living in Linux, but sometimes being required to develop ASP.NET sites — you have no doubt used MonoDevelop. While its latest iteration brings in many good things, it’s still not the ready-to-use Visual Studio.

Once you are past the System.UnauthorizedAccessException and Could not load file or assembly ‘System.Web.WebPages’ errors, you might encounter another weirdo in an imported MVC4 site, an error that prevents loading of default stylesheet(s) in browser. As a result, your site may look completely deprived of any styles, colors, images, etc.

The origin of this error lies in the simple fact that while Windows (possibly the source of your imported MVC site) is case-insensitive with file names, Linux isn’t. Correcting this is as simple as:

  1. opening the file App_Start > BundleConfig.cs, and
  2. changing
  3. bundles.Add(new StyleBundle("~/Content/css").Include("~/Content/site.css"));


    bundles.Add(new StyleBundle("~/Content/css").Include("~/Content/Site.css"));

  4. that is: site.css to Site.css

Merry coding!

My dear ol’ Google Nexus

I’m pretty happy with my Nexus 7. So far, no major complaints. Typing is a breeze. Gaming is fun. Reading books is very convenient. Watching movies is a pleasurable experience. Plus it’s running the latest Android–Kit Kat. For its accessories, I bought an OTG cable and a music case cum carry pouch.

I’m enjoying every bit of this cute little, cheap and quality device. ☺

Posted from my Nexus 7

Cheshire Home


IMAG0960 Before yesterday I had never visited a shelter home as part of a corporate social responsibility initiative, in all my four years of corporate existence. Yesterday, along with a group of volunteers, I paid a half day’s visit to Cheshire Homes’ Delhi Unit to interact with its residents, differently-abled persons. Now I’m not sure how or what changed in me that helped make up my mind for volunteering, but I decided I would go a few moments after receiving a call for volunteering via email. Perhaps it was the apparent approachability of the venue that made me think, “sure, I can give it a shot.” I received the email from our company’s CSR club calling for donations (small, big items) and spending some quality time with people who need it the most. I signed up immediately.

Even when it was two weeks away, I was excited for the visit, for it was going to be a whole new experience for me, personally and professionally. I searched my room for donate-able items, and found some—a couple of unused soaps, shaving gel, and mosquito repellent machines. I dropped these items in the donation box arranged for in our office cafeteria.

Knowing that my office’s CSR club was not particularly known for proper planning, I wasn’t surprised to find out a day before the visit that all volunteers would have to arrange for their own travel. What surprised me was the lack of any defined schedule of events for the visit. What all we were told was that we were going to “spread happiness”. How?—that was a debatable matter, or, as it turned out, the organizers didn’t care about sharing it. Anyway, I reached at the venue, by my own, on time.

I woke up early in the morning and was ready to leave by 8.30am. I took the Yellow-line metro, and changed course from Central Secretariat. Boy! how crowded was the first station of Violet line I cannot express in words, for there were seemingly more people on the platform than there are words in this blog post. It took me close to total two hours in transit, and I was at Cheshire Home at 10.15am. The place impressed me at first sight.

Situated in a posh New Delhi region, Cheshire Home is an expansive shelter home for the under-privileged. The place is more than fifty years old and yet is clean and well-maintained. From a brochure I got from the place, I came to know that it is one in a series of many Cheshire Homes across the globe, a chain founded by Lord Leonard Cheshire. There are 25 Cheshire Homes in India, the Delhi unit being the largest one. Cheshire Home Delhi was established by Major General Virendra Singh in 1957. It has been visited by and received praises from such luminaries as Sonia Gandhi, AB Vajpayee, SD Sharma and PV Narashima Rao. While walking through its passages, it was immediately clear to me why it had been so popular among the biggies.

Read More