This is Part 2 of our blog post about how we used Sitecore to make a Mobile API. To recap, this single API is used to drive 4 different devices, iPhone, iPad, Andriod, and Blackberry. In the first part we covered the highlights of Design Patterns, the RESTful API approach, as well as how we […]
Recently Velir had the opportunity to build Mobile Applications for one of our very prominent clients. One of the challenges was an interest in supporting iPhone, Android, and Blackberry devices. Our content is stored in Sitecore, so we wanted to retain this as the single source of content. Our goal was to build a single […]
The Boston Globe issued a challenge to over 150 developers a few short weeks ago: Build an application in 48 hours to make the city of Boston a better place. Jon Herman and I heeded this call and teamed up with a group of talented GIS specialists and developers to build Boston Green, a mobile optimized web application that helps you find open spaces in Boston.
In the end, our team was honored with the Boston Hack Day grand prize! Read on to find out how we went from concept to award-winning implementation in only a weekend.
Virtually every project that comes through our door at Velir includes a mobile component; a mobile optimized site, a native app, or considerations for new mobile channels (iPad, Kindle, etc.). We recently worked on a project for the Brookings Institution, recognized by Sitecore as an Outstanding Solution, in which we were challenged to:
In my last blog post, I discussed several areas that present challenges when developing native Blackberry applications. I want to conclude with a few related topics that may be of interest to you including; testing, deployment and analytics.
Over the past year, Velir has been diving into the world of native Blackberry applications. As with native iPhone and Android development, Blackberry development carries its own set of unique challenges. Today, I’m sharing our experience to provide the developer community with lessons learned and best practice guidance for Blackberry app development.
This type of view is fairly common in the mobile world, but doesn’t come out of the box with the Android SDK. Think of the home screen(s) on an Android device. You can slide between each home screen and when you lift your finger, it “snaps” to the most appropriate screen. This is fairly simple to build yourself using the existing HorizontalScrollView (or regular ScrollView for vertical scrolling) and adding some code on top of it to handle snapping to each screen. In this post, I’ll show you how I implemented this view for a rotating article feature.