From Cottage to Enterprise: A mobile app journey
Oh, you thought we meant enterprise as in enterprisey? We mean enterprise as in things you people wouldn’t believe.
The mobile development process--as supported by mobile vendors--has been focused on the lone developer in the cottage. When mobile was just a checkbox on your requirements, a small cottage within the enterprise was fine. Will that cut it for you in a mobile-first world? Would you ever allow yourself to release your core server-side code with a click-by-click process in an IDE, relying on a single team member? Then why would you do that for mobile?
We have tackled some of these questions at ReachLocal while building our mobile apps and the LigerMobile open source framework. We don't have all the answers, but we have some of them. Join us as we describe the systems we put in place to build our Constitution-class, NCC-1701 mobile development ecosystem.
- I'm building and releasing mobile apps from one person's desktop, what's the first step to changing that?
- What about testing, how do I test my builds?
- Why should I automate any part of my process and how can I go about that?
- This represents a big change for my mobile developers, how do you recommend communicating such organizational change?
- Does all of this have to be built in-house or are there services for doing some or all of this?
- Robert Tomb, Software Engineering Manager, ReachLocal
- John Gustafsson, Lead Software Engineer, ReachLocal
Robert Tomb, Software Engineering Manager, ReachLocal
Show me another