~ Review of Chrome Remote Desktop ~

Gone are the days where one needed a static IP to access a machine remotely. 5 years ago had explored the options to access my home desktop {a Windows machine} behind a LAN via my MBP {a OSX machine}. Back then it was a tedious process to achieve cross OS remote access. However, there were solutions for PC-PC remote access like RemotePC, LogmeIn. There are others like TeamViewer  & VNC which allowed the same but you have to install the software and get it running.

Coming to the browser era, where the lines are getting blurred between what browsers & Operating Systems {OS} can achieve. Chromium comes in two avatars - Browser & the OS. Google has an App for Chrome Browser called Chrome Remote Desktop, which has come a long way. From Beta release in May 2012 to an App on Chrome Webstore today. The current release of the Chrome RDP stands at Version: 24.0.1312.32. 

The app allows one to remotely control the machine in an OS-agnostic manner when installed. You can setup a minimum 6 digit PIN to control the access to the Remote Machine. Once you have it, you can access the entire machine through a chrome tab. 

For some reason I brought my Windows desktop to life couple of months ago. Today I booted it & wanted to remote control it while I use the MBP as a primary choice. The setup is a breeze & usage has been quite good with one disconnect so far. 

Advanced features of the app can be found here.

~ Fragmentation hoopla ~

Techcrunch posted an article 'This Is What Developing For Android Looks Like' based on a Hong Kong mobile app developer that has seen more than 70 million downloads which performs QA  on 400 different devices. I feel Animoca seem to have used this article to get publicity.

I haven't solely developed an Android/iOS app, but have got my hands dirty in both platforms at some point of time. At SourceN, we do have developers who develop apps Xross-Platform - iPhone, iPad, Android, WebOS. I for sure can say that we do take our quality seriously be it web or mobile apps. Never had the necessity to QA against 400 android devices. That is pure BS & exaggeration of the Nth order to get eye-balls for a company.

I have constantly had debate with people - developers, fanboys (Apple, Off-late Windows), managers - who don't have complete knowledge about how a platform needs to be built than just state that Android would be a failure or disaster lurking in the future due to their OS fragmentation. I have conceded that indeed that would be a problem which Google needs to address with the OEMs & Carriers to ensure that their is very less layer(s) on Vanilla Android.

You have seen Amazon getting away and fork their own version of Android for Kindle Fire tablet. Not sure if that is a good or bad decision which will help them in the long run. Don't think that other OEMs would take such a big bet (Money n Time) to have their own flavors. Considering the fact, many OEMs (HTC, Sony, Samsung, etc) already have their custom layer on Android phones. This itself is causing a lot delay in the latest Android version (ICS) getting ported to various devices in the market.

Many of the OEMs have gone ahead and released boot-loaders where people can unlock and install latest versions of Android OS. I agree this isn't an easy affair for a layman, but is developer oriented. That's another cliché which you get to hear that Androids are more popular amongst Developers than rest of the mankind. 

Don't just complain about Android fragmentation for the heck of it. As with everything in life, there are trade-offs. Fragmentation is over-hyped bubble which is more popularly driven by those who live in the world of tailored walled-gardened & ubiquitous (in simple terms best UX) offering. 

From a developer perspective, if you ever want to understand how the system works here are some articles which is worth reading.

Android fragmentation is a feature, not the big problem everyone says it is
Fragmentation is a Bad Excuse

4.6 iPhone display
Why I'm Not Supporting OS X

P.S: I <3 my MacBookPro & SII :)