What started of as a “small experiment” ended up with me sleepless for 2 days straight.
It all started with this video
Pretty pumped up, I started off exploring the New Polymer. I used Polymer a couple of months ago and wrote a tutorial on Web Components and Polymer . Now, a lot has changed. So, super excited about the new way of developing Web Components, I quickly whipped out 3 new components (<upper-case>, <lower-case> and <capital-case>). Pretty basic, but gave me a decent hands on.
Then I started digging into their tutorial (a must read) and loved the way how components go hand in hand in building an actual application, yet the smaller pieces remain reusable. This got me thinking to make a Hybrid app for my blog using Web Components, PhoneGap and WordPress and this post is the on-going journey.
As of today I was not able to get the Hybrid app working on most of the devices. I was able to get it working only on an iOS emulator (did not test on iPhone/iPad device) and Android 4.4.2 (Android emulator). but I have raised this issue with the Polymer folks.
For the past few days I have been totally digging Google’s Web Starter Kit. Yes, I have used Yeoman, Slush and other “One Stop – Best Practice” tools, but there is something about WSK that makes you want to use it as a Starter template kit for all your projects.
I have been going through the resources and I would recommend the following way to build a new app. Please feel free to share the way you develop too.
Phase I : What’s out there?
First, navigate to Google’s Web Fundamentals. You can find a list of resources on how to build a multi-device web site with a lot of awesome best practices.
In this quick and dirty post, we will see how you can build a static Portfolio website for yourself. We will be leveraging the power of GitHub pages and the default sub-domain that you get when you create an account with GitHub.
We are going a MovieFire app, that will store all your favorite movies. And to persist this data, we will integrate the app with Firebase. We will be implementing the traditional CRUD operations on the movies collection.
Let’s say that you have built a shiny new website and launched it for the world to use. With in the first few days, you keep hearing that the application is slow, and it takes forever to load simple pop-ups, yada yada yada. How do you go about analysing and fixing them?
In this post, we will look at multiple ways how we can dissect a performance issue related to user interface and understand what things you could have done better during your development and testing phase to avoid a situation like this.
As a baseline, we are going to take the example of my blog’s home page. If people reported that my blog is loading slowly, the first thing I would do is go to Pingdom and run a page load test. And the results would reflect as
This seems kind of okay, with a load time of 2 seconds and page size just about an MB for the home page of my blog.