Dell Boomi clients wanted to launch new technology capabilities that will rapidly deliver a competitive edge. Unfortunately, project backlogs and multiple priorities often slow the pace of innovation. Overworked and understaffed IT teams often compound this problem, resulting in employee turnover that makes it even harder for businesses to retain the best and brightest IT staff.
Ultimately, the cycle of pressing priorities and strained IT resources leads to a skills gap that causes many companies to lag behind.
And integration is central to this issue. These days organizations need to be extremely agile in how they integrate their applications and data to drive digital transformation. The volume and diversity of integrations necessary for running a digital business are growing exponentially. Social, mobile, analytics, big data, IoT and AI technologies all require integration into core business systems.
And integration is fundamental for any organization…
This Thursday, May 28th 2015, I was able to attend Google I/O Extended at their Cambridge Massachusetts campus. A special thanks to the Boston Android meetup group for the invitation!
Of course, Google had a plethora of announcements. Here are some of the most interesting ones I took away, in no particular order.
When choosing a Mobile Device Management (MDM) solution there are many features that need to be considered, along with pricing and hosting models. The world of MDM can be cumbersome and confusing, so it is important to understand what is out there.
A recent project required me to create an Android ListView looking like the “out of the box” IOS ListView which separates the items by letter and has the letter at the top of each letter section (IOS example below):
Since there is no switch in Android Development to just turn this feature on, I created a generic library that can be customized and themed to fulfill these needs. This library can be pulled from our GitHub repository.
Recently I attempted to create an application that worked in an “Offline” mode. However one of the biggest hurdles I encountered was maintaining the data model throughout development. As most projects go, the definition of the database tables changed frequently, and maintaining the structure became a tangled mess of version numbers, alter statements and data migration scripts. In trying to solve for this problem and adhere to good practices, I created classes that stored my column names and indexes so I could later read them back from the cursor. Trying to add columns, though proved to be very code intensive.
After scrapping the idea due to a tight time line, I began researching other solutions in the JAVA/Android community. I came across GreenDAO ORM (http://greendao-orm.com/). It is a complete code generation which allows you to generate your data model without having to…
So, you’ve finished the initial development of your new Android Application, resolved all of the obvious bugs, and now you are ready to get it out there for additional testing. There are numerous ways this could be done, but if your ultimate goal is to publish your app in the Google Play Store it is a natural choice to use the Play Store itself for Beta testing.
While looking for the best way to implement an input widget to retrieve the users’s Date of Birth I came across this input field while editing a contacts information in the generic People List that comes with the Android OS:
In recent years, the boom in mobile devices has caused more and more users to abandon their desktop internet browsers and opt for the ones sitting in their pocket. As a result, nearly 10% of 2011’s internet traffic was attributed to mobile device browsers. As more people are browsing the internet in this manner, it is important that currently standing websites, as well as newly developed ones, also include mobile friendly pages in their site.
Many companies have followed models put forth by sites such as www.amazon.com, with their widely known desktop interface for purchasing products. When the mobile markets started to pick up they developed a mobile site that operates in much the same way, but offers a friendlier user experience for those viewing it on a smartphone screen. This move to a mobile intuitive platform can generate an increase…
Android SDK (version r11)
Robotium (version 3.0)
Automated tests are key in maintaining high quality software. They help catch bugs immediately when introducing new code and also ensure that new features do not conflict with existing functionality. Another advantage of automated tests, specially for Android applications is that it greatly speeds up testing when you have multiple builds for different devices. In this blog post I’ll go over how we use robotium in our TASS mobile project to implement automated black box tests.
Robotium is a plugin that extends existing instrumentation tests available on Android and addresses its shortcomings. Limitations such as slow execution times and having to manually delay the application to wait for the desired screen to be ready. For example, delays caused by waiting for a network request to complete before proceeding to the next screen. Robotium works by sending…
I will assume the following has been installed and configured.
Android SDK (r07 or later)
Maven 3 (version 3.0.3)
Set environment variable ANDROID_HOME to point to the root directory of the Android SDK.
Add ANDROID_HOME/tools to your PATH environment variable.
An Android project to build
Building an Android project consists of 3 steps. The code is compiled to create an executable apk file, then the apk is signed and finally zipaligned to optimize disk space usage on the mobile device.
Executing these steps manually is prone to human error and can lead to bad builds. This can happen due to forgetting to sign the package, missing dependencies, etc. It is also time consuming especially if you have fast iteration cycles and/or multiple build configurations for different version of the Android OS. Using Maven and android-maven-plugin we can create a one step process to manage dependencies, build, sign and…