Finally, after quite a while, we found some free time to work on Android persistence library I wrote about in this blog post. Knowing we have very tight schedule, as always, we wanted to make sure library is ready to be used. So, we took a good look at what we did before, rolled up our sleaves and got to work.
Main goal was to make library stable and useful. In order to achieve that, some of the functionalities were reimplemented, some new were added and some were removed. There is no sense in having some features that are not part of any complete logic representing only fractions of future functionality set. Since those are useless if looked upon separately, they could only confuse person who is using the library.
Android persistence accelerated – revisited
category: Android, Java, Mobile | 
no comment
This post is written on May 10, 2012 by Dusan Zamurovic
Continuous Integration for iOS projects with Jenkins CI
At codecentric we are using a central Jenkins continuous integration server to build all our software modules automatically after every check in procedure. The status of all builds is permanantly visible for all employees through screens in the offices and beside the coffee machines. This gives us transperancy about all our software modules. All modules? - Oh well, at least about all our Java and Android modules. But what about all these tiny iOS applications? As iOS apps do not compile on our Linux based build server these modules abscond themselves from showing up on our build monitors.
This needs to be changed. This article is a step by step introduction showing you how to integrate iOS builds in an existing Jenkins CI build infrastructure. (read more…)
category: Continuous Delivery, iOS, Mobile | 4 Comments so far
This post is written on January 9, 2012 by Lars Rückemann
SOAP web services with iOS
Judging by the looks of current web platform APIs, like those of social networks, Amazon’s web services, photo sharing sites like Flickr or Instagram and many more, one could get the impression that REST has fully replaced the much maligned SOAP as the underlying communications architecture.
However, this is only true at first glance. Lots of company internal or B2B services are implemented with SOAP – especially where there is a need for more complex operations than in typical CRUD scenarios – or for more complex data structures and formal function signatures.
First things first though: This post is not about comparing advantages and disadvantages of REST and SOAP or a discussion of whether they should be compared at all – others have done that at great depth already.
Instead, this is about those cases where the decision for SOAP and against REST has already been made and where you now have to implement an iOS application that acts as a consumer of SOAP services.
The use of SOAP sometimes has historical reasons, because it might have already been established before REST became popular. But using it can also be a conscious decision, e. g. when a formally verifiable and very explicit specification is required for internal or external consumers.
category: Java, Mobile | 2 Comments so far
This post is written on January 2, 2012 by Daniel Schneller
English 
Deutsch 
