IMImobile to drive innovation in multi-device applications across web, mobile & social channels.

IMImobile, a leading provider of technology infrastructure for mobile data, voice and video services to mobile operators, enterprises and media companies today announced the acquisition of UK-based digital agency Skinkers.

Skinkers pioneered the use of desktop applications since early 2000 and more recently has developed innovative iPhone/iPad and Android applications for some of the world’s biggest and best-known organisations and brands. Its client list includes the American Airlines, BBC, Haymarket, Microsoft, NDS, Spectator and Virgin Atlantic.

Vishwanath Alluri, Founder and Chairman of IMImobile commented “With the acquisition of Skinkers we will add considerable strength to our existing offering. Skinkers bring on board an excellent digital understanding of application development, user-interface design as well as great expertise how to best use the latest web and social network technologies.”

For more information and the full press release please click here.

Well, it doesn’t seem like 2 minutes ago since we moved last, but our time in temporary accommodation has come to an end and we have finally planted our roots firmly in Soho.

Skinkers is now located at:

After many happy (and sometimes noisy) years, Skinkers have relocated from Kirby Street in Clerkenwell over to Beech Street in Barbican.

All phone and fax numbers are the same but our address has changed to:

Who would have though that Leather Lane market could be beaten? We’ll miss you, but hello Whitecross Street market!

When using setTimeout or setInterval in IE, there is no way to pass any data to the method you want to execute.
You can obviously create lots of global variables, but this is a very messy solution, and not object oriented.

Similarly, if you are using an API that makes an A-Synchronous call and you can set a callback handler, you may well want to pass extra data to the handler, and the API may not let you.

To get round this you can use a delegate function. You basically tell another function what to execute, what to pass it and the scope to execute it in.

NOTE : This method uses jQuery for browser detection. However you can add whichever browser detection you like and replace the $.browser.mozilla check in the method.

/**
* @param scope Object :  The scope in which to execute the delegated function.
* @param func Function : The function to execute
* @param data Object or Array : The data to pass to the function. If the function is also passed arguments, the data is appended to the arguments list. If the data is an Array, each item is appended as a new argument.
* @param isTimeout Boolean : Indicates if the delegate is being executed as part of timeout/interval method or not. This is required for Mozilla/Gecko based browsers when you are passing in extra arguments. This is not needed if you are not passing extra data in.
*/
function delegate(scope, func, data, isTimeout)
{
	return function()
	{
		var args = Array.prototype.slice.apply(arguments).concat(data);
		//Mozilla/Gecko passes a extra arg to indicate the "lateness" of the interval
		//this needs to be removed otherwise your handler receives more arguments than you expected.
                //NOTE : This uses jQuery for browser detection, you can add whatever browser detection you like and replace the below.
		if (isTimeout && $.browser.mozilla)
			args.shift();	

		func.apply(scope, args);
	}
}

The delegate function then creates another function, that will execute your original function and pass it all your data. This new function requires no arguments and is de-coupled so it does not suffer scoping issues when being passed between objects.

This example shows how to create a delegate method…

//Our function to execute via the delegate
function helloFunc(name, age)
{
	alert("hello " + name + " you are " + age);
}

//Our delegated function
var delegateFunc =  delegate( this, helloFunc,  ["Bob", 50] );

//Now we can execute the delegate function, passing no arguments to it and we see our data alerted.
delegateFunc(); //hello Bob 50.

You can also pass data into the delegate, which will precede the data set when the delegate was created.

//Our function to execute via the delegate
function helloFunc(message, name)
{
	alert(message + name);
}

//Our delegated function
var delegateFunc =  delegate( this, helloFunc,  "Bob" );

//Now we can execute the delegate function, but this time we pass it some arguments. Both these arguments, and our delegated arguments are all passed to the delegated function.

delegateFunc("Welcome to my site"); //Welcome to my site Bob

In the case of setTimeout, you can simply execute the delegate in line as it returns the function reference.

UPDATE: due to Mozilla’s implementation of intervals / timeouts we need to pass a flag to indicate the method is executing as part of a timeout callback. This is due to the fact mozilla will insert an extra parameter indicating the “lateness” of the timeout. More here.

	setTimeout( delegate( this, myFunction,  "hello", true), 5000);

Or in the scope of another object, with multiple arguments as an array

 	setTimeout( delegate( myObject, myFunction,  ["hello", 10, someData], true ), 5000);

When using an API, such as the google gadgets API to load data, you might want to pass extra data through, the delegate works here as well. As it appends arguments, any data passed by the API is still preserved, the delegate will just add your extra arguments to the end of the arguments already passed to the callback.

gadgets.io.makeRequest( myURL , delegate(this, dataSourceLoadedHandler, ["bob", 50]), params);

//Response is passed by the Google API,
//Name and Age are appended to the arguments list by our delegate
function dataSourceLoadedHandler(response, name, age)
{

}

Delegating is a much cleaner and more object oriented approach than littering you code with global variables.

.m

A bit of background info

Hi everybody, I wanted to give you a little update on how our experience with Lync has been so far and how are we doing device-wise.

By now we completely replaced our legacy 3CX environment and sold most of the old Linksys SPA941 phones we used with it. All these phones had to be replaced with new, Lync compatible ones though. We did a pilot experiment to see if people were ready to just ditch their deskphone and use headsets all the time. As you can guess the answer is a big fat NO. A handset is just too convenient to have, you can’t expect sales people and developers to be wearing a headset at all times as if they were in a call centre, so the result is that many calls were going missing, etc.

That’s when I started exploring which alternatives were available. The key requirements for most people were:

• Being able to use the phone regardless of their computer being turned on and Lync logged in
• Most users were happy with having basic functionality on their phone (making phone calls, receiving them, joining a conference) and would use Lync client for more high-level functionality

With these two requirements in mind, we ruled out all the USB handsets (Polycom CX200, etc.), it had to be Ethernet, and possibly not break the bank.

So we started talking with Snom, who have been developing an OCS compatible firmware for the past years, which runs on most phones they produce. They have been extremely kind and agreed to send us a sample of three models they distribute which support the OCS firmware:

• Snom 300 – a no frills phone perfect for people who don’t live constantly on the phone, or for communal areas
• Snom 821 – a nice colour display phone which provides enhanced presence, and advanced telephony features
• Snom 870 – their top-of-the-range touchscreen phone, suitable for power users and management

Now, if you used an Aries-based Lync Phone before (e.g. Aastra 6725ip, or Polycom CX600) you will be accustomed to the ease of deployment these phones enjoy, just plug it into the Ethernet, and via USB to the computer, and Lync client will deliver all the necessary settings to the phone, ask you to enter your password and presto, you’re all set.

The problem with Snom phones so far, instead, was that the user was either required to type in his SIP uri, domain, username and password using the clunky phone keyboard, or find out the IP of his phone, open the web interface and do so via web. Not the easiest experience for an end user, especially if not technically minded.

But this now has changed thanks to a great piece of software developed by the Sydney Harbour Foreshore Authority, which automates the provisioning of Snom phones into your environment.

Snomtastic!!

This is what the Hardware inventory looks like in Snomtastic

Snomtastic does many things, and covers all the functionalities one would expect from a mass deployment provisioning tool:

• Hardware inventory
• Remote reboot
• Multiple configurations
• Firmware updates
• Easy login for the users

The easy login part is covered with a tiny client utility you can easily deploy by group policies, which asks the users to enter their Active Directory credentials, and automates the login on the phone, mimicking the experience you’d get by using a normal Aries/Tanjay phone.

Unfortunately, because the software is not in production stage yet, the installation process is very manual and prone to issues with the webserver (e.g. if you run a 64bit version of Windows and IIS you will have to do a few undocumented tweaks to the IIS settings), but our friend Drago Totev wrote a super-detailed how-to in four parts on how to get up and running with Snomtastic. He will also provide you a copy of the database back up with a few tweaks to support newer phones.

To be honest I don’t feel like I need to add anything to the excellent job he did at writing that tutorial, it literally covers everything, also the firmware updates. With a bit of patience everybody can get Snomtastic up and running by following it.

One thing we hope to see in future Snomtastic releases is the ability to add more managed settings to the ones available via web interface, while now it requires changing the database schema by hand. I can see this becoming a key feature as Snom releases newer versions of the OCS firmware which add support for additional settings (i.e. the server-controlled remote keyboard lock option which appeared in v8.6.6.4).

The only caveat I found so far, is that if you try to reset a provisioned phone to factory settings, it will still hold some parameters in the memory, and you’ll end up locked out from its web interface. None of the factory passwords worked for me to gain access to it again. The only solution is these cases, is to follow this procedure and flash the phone with the recovery firmware, then re-flash it with the latest OCS firmware (make sure to be on a network where it won’t pick up the DHCP option 66 again, or you’ll be back to square one).

So, there you go: by getting Snom phones and Snomtastic you’ll have an easy-to-manage environment, with high quality Ethernet desk phones, without having to compromise on price and get USB handsets of limited functionality.

After getting confused for the millionth time regarding converting Density Independent Pixels to Pixels (or vice versa), We decided to create a simple calculator to do it for us!

This should help to determine what size to make all your assets so you can support multiple screen densities on Android.

Android DP / PX Calculator

Android API : Supporting Multiple Screens

m.

The brand new ‘New Media Age’ app for the Apple iPhone is now available for download from the iTunes App Store.

NMA iPhone App

The app builds on the success of the original NMA app that was launched last year, and includes these great new features:  - All content is fully available offline, allowing you to read news and opinion even when you don’t have a connection to the Internet. - Share articles with your friends across key social networks such as email, Facebook and Twitter. - Read the latest from Gadfly. - A complete UI re-design. You can download it from the link below: http://itunes.apple.com/gb/app/new-media-age/id340427952?mt=8 The app takes full advantage of Skinkers’ products and technologies, including the ‘Application Accelerator’ product and ‘Content Services’ cloud service.

Skinkers moves to strengthen its app building capability by purchasing Umee.

Skinkers Limited, well established Technical Agency and proven supplier of push communications and desktop alerts technology to some of the world’s biggest and best-known organisations and brands such as the BBC, American Airlines, UPS, Aviva, Virgin Atlantic and Microsoft, today announced the acquisition of Sprawl Technologies Limited, owners of Umee. Thus, instantly extending and enhancing Skinkers mobile development division with new capabilities, technology and sought after skills.

Umee (umee.tv) is a leading mobile development specialist who works with publishers and content owners, providing them with highly effective ways of reaching their audiences on mobile devices. Umee have delivered successful apps and sites for iPhone, iPad, Android and BlackBerry for clients such as New Media Age, Wallpaper Magazine, Annabel Karmel, the Daily Telegraph, NME Magazine, Brand Republic and Jaguar Cars.

“We are delighted to announce our acquisition of Umee today. They bring valuable mobile skills, experience and technology to the Skinkers team and its clients. Combined with Skinkers’ experience of building complex and highly integrated desktop applications such as BBC iPlayer Desktop, we can now offer our clients engaging and effective solutions across all platforms – web, social networks, desktop and mobile” says David Long, CEO Skinkers

All Umee’s staff will be retained and operations will be moved into Skinkers London HQ this month.

“The match between Umee and Skinkers is excellent; both companies have a history of innovation and technical excellence. Our skills and experience are highly complementary and I look forward to working with the Skinkers guys” commented Andrew Hawkins, CEO Umee.

About Skinkers
Skinkers is a Digital Agency that helps its clients plan, create, and manage innovative technical solutions across a broad range of digital media. With our award-winning, talented and highly experienced team based in central London, they provide an extraordinary understanding of all digital platforms to help bring your online strategy to life.

Skinkers technology is used by many of the world’s leading brands including the BBC, Aviva, Capital One, Zurich Insurance, NHS, Premier League & American Airlines.

skinkers.com

For further information

Rob Noble
rob.noble@skinkers.com
+44 (0)207 036 6580

Skinkers’ TouchSwipe jQuery plugin enables the detection of swipe gestures on touch based devices.

Features

• Detects swipes in 4 directions, “up”, “down”, “left” and “right”
• Supports single finger or double finger touch events
• Supports click as well as swipe
• Definable threshold to determin when a gesture is actually a swipe
• Events triggered for swipe “start”,”move”,”end” and “cancel”
• End event can be triggered either on touch release, or as soon as threshold is met
• Allows swiping and page scrolling

Download the plugin at :
http://plugins.jquery.com/project/touchSwipe

Demos and docs at:
http://labs.skinkers.com/touchSwipe/

During our Lync 2010 deployment we had some problems with AIM connectivity, with the following symptoms:

• Presence would take up to 30 mins to update on both clients
• Messages in both directions would get lost 90% of the times, with some random ones getting through
• Lots of 481 “Call Leg/Transaction does not exists” errors coming up in the SIP Stack log on the edge server

I had to work this out with Microsoft, and as it turns out it’d have been a very difficult one to debug. The bottom line is that when the provider of your public Lync Edge UC Certificate uses different SSL Cyper Suites from the ones AOL expects, it will try them all until it will eventually timeout and return errors, which happens most of the times.

The following solution will change the order of the Cyper suites and magically AIM will start working fine.

UPDATE: The original author of this solution is Scott Oseychik. I simply got this solution from a Microsoft Support Engineer and wasn’t aware about this blog post: http://blogs.msdn.com/b/scottos/archive/2009/04/03/resolved-ocs-2007-r2-pic-fails-against-aol.aspx - Thanks Scott!