November 11, 2008
When the time comes to test how various implementations of different types of browsers actually work with a particular application, much trial and error still exist. Despite the rise of application testing services in the cloud, testing browser compatibility against a production application is still problematic. More often than not, when testing does occur, it’s against a replica of the application running in a different environment, being accessed by browsers that might not even have any of the plug-ins that the application may need to support in a production environment.
This week Apple announced that they are restricting NFC radio access, supporting only Apple Pay in the upcoming iPhone 6 and 6 Plus launch, which is a big downer for developers.
The thing about agile development is that for all intents and purposes an application is never done. Successive waves of updates to an application means that development teams have to come to terms with the simple fact that the care and feeding of any given application is a continuous process that takes place over many years.