Posted by Jeroen Leenarts in the wee hours: February 11th, 2012
Recently I started working for Xebia and what better way to introduce myself with a nice blogpost and some free code and some explanation to go along with it.
To get you started: here is the code. It’s on GitHub so don’t be afraid to send in suggestions and whatnot. (more…)
Posted by Urs Peter in the early evening: December 5th, 2011
Being relatively new to html5 and mobile development I spotted an excellent opportunity to catch up with the latest trends during the QCon conference in San Fransisco where they offered a wide variety of html5 and mobile tracks.
In this blog I’ll share the insights I gained during the conference. After reading it you should have an overview of the following:
- where html5 is right now and where it is heading to with regard to mobile development
- the benefits and drawbacks of html5 for web-apps compared to native apps
- how to bridge some of the shortcomings of html5 with regard to native apps
- valuable pointers to resources helping you to get started with html5 mobile development
Posted by Arno den Hond at around evening time: November 14th, 2011
Unlike announced in my previous post this one is neither soon nor on a surprise topic. It is about a general aspect of Android that is, to my opinion, very powerful but often under utilized.
Android apps are not monolithic but rather a collection of components of different kinds. I suspect android took inspiration from the concept of midlet suites in j2me and believe it expanded on that quite well.
These components (except for provider) can be exposed through intent filters in the package’s manifest and can be used by other components in different packages. This allows apps to accomplish tasks together which a single app could never do.
(more…)
Posted by Jan Vermeir in the early evening: September 13th, 2011
With everybody going mobile, we could not stay behind. This meant we had to create an Android application, because we (Bram Neijt, Arno den Hond and your chronicler) do not own one of them fancy iPhones.
Also, Android is way cooler.
(more…)
Posted by Arno den Hond in the late afternoon: July 6th, 2011
As pointed out in an earlier post the importance of testing can not be understated.
In this post we will delve into BDD of Android apps.
There are a number of other testing tools for Android out there, such as Robolectric and Calculon. Robolectric improves the speed of running the test by executing it outside of the emulator. Calculon is a DSL for testing views and activities. As Robotium seems to most mature and reliable, it is my preference.
Posted by Gerbrand van Dieijen mid-afternoon: May 31st, 2011
Last weekend the public beta of JavaFX 2.0 came out. I’ve much anticipated this release, as you might guess from my previous posting on JavaFX 2.0. I’ve downloaded the JavaFX-runtime, SDK and Netbeans-plugins the following evening from Oracle’s JavaFX page and started trying out JavaFX by viewing and running the examples from the SDK from Netbeans.
I’m quite enthusiastic, read on the learn more!
(more…)
Posted by Robert van Loghem just before lunchtime: March 23rd, 2011
Last time I explained why I think doing TDD for mobile is imperative, and why I do it. But now it’s time to get technical, and explain to you how to set up, GHUnit in XCode 4 and run unit tests, not only in the iPhone and iPad simulator but also on your own physical device!, it’s in text and images but also in video form on YouTube.
Note, if you want to know why i chose GHUnit over OCUnit, just scroll down to the end of the post.
Posted by Robert van Loghem around lunchtime: March 9th, 2011
Since a couple of months I’ve been developing mobile applications, some are for the business at home (girlfriend-shopping-list app that actually works and augmented reality garden iPad app) and some are for work. I have experienced that TDD and Continuous testing (Test Driven Development) is a way of working that leads to fewer bugs and regression problems and better design in my software, it’s my preferred way of programming, not testing.
And to start off, here’s how I benefit from doing TDD:
- Robust
- Better code design, no really!
- Find regression problems early on
and you can read more on TDD and Continuous testing here.
The thing is, writing a mobile app takes about 20% of the time it would take me to write a web+client+server based app. Which of-course is really nice, because I can write lots of apps. It also means that whenever i need to fix a bug or add new functionality, I need to have developed it in a TDD fashion, otherwise i cannot guarantee reliability. So let me explain why…