Nothing new this 2 weeks. Well, in fact tons of new stuff this 2 weeks, but no time to blog at all. We are experiencing extreme-2-week-game-development and are almost ready to release “how not to screw up big projects” book (this is a joke, everything’s under control).

Meanwhile, we posted some stuff at codebranch blog, and want to say “HI” to our folks at LeWeb in Paris this week ;)

You can read this:

How to Accurately Estimate Projects for Outsourcing? Part I – Delays Caused by Communication

In addition to that, there’s been quite a few times, when our clients from other countries needed to clarify detailed info with a a third-party with no people on that side speaking English at all.
The main point of this section is to make you understand how heavily client interaction lag can affect the entire project. It’s worth mentioning because these things rather frequently fall out of scope of attention.

How to avoid possible adverse effects? A checklist or a roadmap will be helpful to manage handling tasks in advance. In Codebranch, we prepare a project roadmap with Freeze dates, which are the last dates that a certain part of team-client interaction is due

How to accurately estimate outsourcing projects. Part II: Accessing Web Services

1. Compatibility and environment issues.

The most common problem though is the environment. Whether it’s an API, a plugin to work with it, it may require additional adjustments to your server. Documentation should be carefully revised so that there are no flops when integrating the solution into your own website or service.

2. Sometimes a client wants solution for a service, that has no public API. i.e. Pinterest has no public API and provides a gateway just for iOS.

Developers start to use workarounds, gather together to find solutions. And so – 3rd party APIs are born. Returning to Pinterest, as a great example, apps that use 3rd party API access Pinterest via iOS gateway, identifying themselves as iPhone. Of course, that won’t always work as expected, even minor changes in Pinterest API now breaks almost every single app that uses 3rd party API.

See you guys when I’m free ;)

Recently LongZheng mentioned that MS Research announced that it will ship JS library for Kinect-enabled websites on Interactive Tabletops & Surfaces conference. Find out how could this affect interactive web in perspective:

Read the full article here

Today’s approach for developing Kinect applications is the same as any other involving sensors: you take the SDK, create an app, connect the device and test it, get the data you need. JavaScript library for Kinect-enabled websites could help merging the application development, limiting the functionality but making the solution more universal. Just imagine: you create a website with an interactive kinect-enabled module. Of course, talking about Microsoft’s piece of technology, we get a platform limitation: feature is IE only. Features are delivered via ActiveX, and that means no support for other browsers. Good news: IE9 and 10 are much better than the older versions and are capable of rendering great websites (almost) correctly.

Having worked in the sound recognition field in mobile space (bird sounds) I know about this hard process a bit. Mostly I was using predefined algorithms and just implemented them in c#, but my poor knowledge and puny brain would never do such amazing stuff!

Natural UI comes to life! You can always see that some awesome MS Research powered speech recognition displayed on MS keynotes almost in real-time, but yesterday’s article on The Next Web highlighted the new addition to that wonderful feature: same voice tone speech translation in Mandarin! Check this out!

Source: Microsoft Demos Amazing English to Mandarin Translation, Allowing for Real-Time Audible Translations

Here’s a bit of a post I’ve wrote, shared my thoughts on the rumor of Apple thinking about moving from Intel archtecture to ARM one. I tried to not dig too deep into the tech field and specifications, because I’m not an expert in CPU’s architectures, but I know the basics and I guess maybe someone will be interested =)

Click here to read the full article

There is a good chance, that Apple is already testing some prototypes deep inside its labs, but it’s a huge work on optimization to be performed, and the OS could become fragmented. As it is with Windows 8 on x86 and limited Windows RT on ARM.

ARM-supported version of OS X should include an emulator-cushion, same as Rosetta, Apple provided for PowerPC => x86 transition. AllthingsDigital states that there is an example: Russian Company successfully runs x86 software on ARM.

Such scenarios could happen: development-wise it’s Cocoa for the UI. And the app that calls windows will still do that on ARM version. Apple has developed an awesome IDE that simplifies the process of development between OS X and iOS. But running x86 code on ARM with the emulator could help if we’re talking about the simple applications that call the standard UI libraries and common stuff like that.

Follow

Get every new post delivered to your Inbox.

Join 325 other followers