FedEx Mobile on iOS iOS native app
Focus
iOS Native, Backend REST/Java services
Responsibilities
Concept, Design, Coding
Timeline
Early 2008
Thoughts
In 2008 the future of the Apple iPhone was far from set. The moment I heard the announcement of the API and the App Store I knew we needed to be there. Within an hour I was on the phone presenting concepts.
The first release of FedEx Mobile on iOS was a great success. Developing a new application in a new ecosystem in a new environment for a new platform under very tight timelines was hard enough, but we needed middle-tier services built as well.
Design
As I set out designing the first version of the application I wanted to stay close to the Apple guidelines since user adoption would be new to almost everything. But I was intent on bringing the brand identity I had forged with Advanced Tracking and FedEx Desktop — including the Placard — to this new platform.
Doing this created a consistency with our customers that resonated. Feedback was positive and rewarding.
Technology
The first version of the client stored data in structured files locally to maintain an online/offline behavior pattern where customers could still use the app and most of its features while on a plane, for example. Then changes would be sent to the middle-tier services once connectivity was returned.
The middle-tier services that I designed and wrote in conjunction with another teammate were RESTful in nature and behavior. We leveraged a light-weight generic Java servlet architecture I had been working on since Advanced Tracking.
Delivering both layers of products in a short development cycle was critical and gave more reasons to continue with our Agile-like team patterns.
