Finally getting around to posting about my experience at this year’s Steel City Codefest where I worked with a team of my colleagues to whip up a prototype of an app for a non-profit organization: TheCheckpoint.org.
This particular project was to create a mobile app (cross-platform) for veterans to locate and review/rate resources and services. While this doesn’t sound like a particularly flashy application to work on, we felt it was one with more need than the others (plenty of teams volunteering for other projects) and the challenge was really to try to make something useful and interesting.
THE TEAM AND THE TECH
Initially I had no plans to participate in Codefest but a few of my colleagues at work were joining in so I figured I would give it a shot. We all have many years of experience working on a variety of technologies but we all shared a common background for C#/.NET so we decided to leverage Xamarin’s cross-platform native app framework so that we could all contribute as equally as possible. Since we were targeting both iPhone and Android we felt that we were too limited by a hybrid-mobile solution and didn’t have a big enough team to go full native (Objective-C and Java) so Xamarin fit right in the middle.
Additionally, we wanted to share as much code as possible (really the only way to recoup the cost of tools/platforms like Xamarin) so we decided to incorporate MvvmCross, a framework for Xamarin allowing us to only need to re-write the view layer and share all the way down through the ViewModels and so on.
While we had done some initial planning after work, we pretty much came in with a blank slate ready to get started. As I was the only one with a MacBook, I was on the hook for ripping out the iPhone version, Geoff had some Android experience so he was tackling that, Mark started working through integration with FourSquare, and since our designer was a no-show, Steve got stuck with the UX/UI design work and also kicking in on the ViewModels.
15 straight hours of coding later and out pops a prototype of an app:
I am planning on finishing this app as soon as I get a chance to get working on it. To help, I am working with Jared from Checkpoint to apply for some grant money to cover the cost of licenses (Xamarin), services (some mobile backend-as-a-service) and some time/help/kindness of others!
Pittsburgh Tech Fest was great this year! It was a perfect opportunity to learn about some different technologies and techniques. I’d like to give a special thanks to Dave and Eric for doing an awesome job organizing the event and the speakers.
For those that are interested, below are the links to the talk I did on iOS Best Practices: Avoid the Bloat and feel free to comment or ask any questions on this post!
Code before refactoring: https://github.com/JAgostoni/iOS-Best-Practices/tree/master/UglyApp
Code after refactoring: https://github.com/JAgostoni/iOS-Best-Practices/tree/master/NotSoUglyApp
Code as presented at Pittsburgh Tech Fest: https://github.com/JAgostoni/iOS-Best-Practices/tree/master/PghTechFest
PowerPoint Slides: iOS Best Practices – Pittsburgh Tech Fest
PDF Slides: iOS Best Practices (PDF) – Pittsburgh Tech Fest
Thanks again to those that attended my talk!
One of the more challenging things in creating iOS applications is the whole provisioning and deployment process. This becomes especially true during beta testing of your application using Ad-Hoc distribution.
The process is something like this:
- Gather all the UDIDs from your test subjects
- Enter these into the iOS Provisioning Portal
- Create a distribution certificate (if you haven’t already)
- Create an Ad-Hoc provisioning profile
- Download the profile and certificate
- Configure and build your app signing with these credentials
Then, your testers need to get the application and install it. Generally like this:
- Email the testers the provisioning profile and app bundle
- The tester need to drag both to iTunes (or Organizer) and then tether and sync
This makes it a little cumbersome for most testers and difficult for non-tech savvy users. One could post the app bundle to a website with a manifest and then create a launch page (like an internal app store) and then notify the users. This is where Test Flight (www.testflightapp.com) comes in … managing the web-delivery of your application in a really easy-to-use process.
Remembering the above, now I do this:
- (optional) Ask your test users to register their devices
- (optional) Create a team out of these testers and download their device IDs
- (optional) Upload all of these device IDs at one time to the Provisioning Portal
- Follow the same process as above to create a provisioning profile and build
- Now upload the IPA bundle to Test Flight and I am done
At this point, the testers can receive a notification of the new build (and subsequent builds) and simply visit Test Flight on their device. They will be able to install your beta app straight from the browser. Further, I can report on who has installed the app and who has not.
All this and the website has a nice easy to use design on top of that!