10Nov/14

Building business apps for mobile devices should be easy (part 3)

This is the third blog of series of three. The first blog covers how Native, Hybrid and HTML Mobile App Types Compare and the second blog covers a variety of criteria you need to analyze before you can decide on the Development Tools.  This blog series is complementary to the Webinar "Understanding the key pieces of Mobile app development" and based on an article by Richard Lancaster, published by MC Press at http://www.mcpressonline.com/wireless-/-mobile/you-want-to-build-business-apps-for-mobile-devices.html#sthash.G9xwG1TP.dpuf 

This third blog covers the topic of Development tools for Mobile apps.  It provides an overview of
-  Available development tools for Native, Hybrid and Web mobile apps.
-  Mobile app development/delivery options, considerations and consequences.
Continue reading “Building business apps for mobile devices should be easy (part 3)” »

4Nov/14

Building business apps for mobile devices should be easy (part 2)

This is the second blog of series of three.  The first blog covers how Native, Hybrid and HTML Mobile App Types compare and the third blog covers Development Tools for Mobile Apps. The blog series is based on an article by Richard Lancaster, published in MC Press at http://www.mcpressonline.com/wireless-/-mobile/you-want-to-build-business-apps-for-mobile-devices.html#sthash.G9xwG1TP.dpuf and complementary to the Webinar "Understanding the key pieces of Mobile app development"

This second blog covers:   
   -   Which business processes and transactions to mobilize
   -   How the target audience may influence design and platform decisions 
   -   Considerations for buying apps or building your own
   -   Criteria for choosing a mobile platform  Continue reading “Building business apps for mobile devices should be easy (part 2)” »

22Oct/14

Building business apps for mobile devices should be easy (part 1)

This is the first blog of series of three titled “Building business apps for mobile devices should be easy”. The blog series is based on an article by Richard Lancaster, published in MC Press at http://www.mcpressonline.com/wireless-/-mobile/you-want-to-build-business-apps-for-mobile-devices.html#sthash.G9xwG1TP.dpuf and complements the Webinar "Understanding the key pieces of Mobile app development".

This first blog covers the topic:  How Native, Hybrid and HTML Mobile App types compare

Building business apps for mobile devices should be easy.  Firstly, the physical features of mobile devices impose limits on memory, storage capacity and screen size.  Secondly, mobile apps typically satisfy a narrow set of business requirements. One might expect that the device constraints and a narrow requirement domain would simplify the task of building mobile apps. However, building business apps for mobile devices can be hard work, especially for companies that have little experience in mobile development and are embarking on new projects. 

Continue reading “Building business apps for mobile devices should be easy (part 1)” »

22Sep/14

User Interface Design – Less is so much more

Just because you can doesn't mean you should

“How old were you when you got your first phone, daddy?”, asked my 8 year old daughter. She looked shocked when I told her I was 28 and it was 1997. She was just as surprised when I told her that I sent my first email when I was 26 and used a browser for the first time that same year. She was even more shocked that the first iPad didn’t exist until 2010. In fact, she was so shocked that she looked it up on Wikipedia on her iPad just to confirm I wasn’t kidding. 

I told her about telex, fax machines, computers that filled a room, office circular memos that went from in-tray to in-tray, and how we sent letters that took several days to get to their destination.  She told me it all sounded very weird. Looking back, I might be inclined to agree with her. Compared to today’s marketing driven, connected world, it does seem a little quaint.      Continue reading “User Interface Design – Less is so much more” »

19Aug/14

Mind the Gap: Addressing Ambiguity in Requirements

The lesson of the Tower of Babel, possibly the first post-project review in historical records, is that communication failure within the team will cause project failure. In today’s projects, often staffed by cross-functional teams spread across the globe, the communication challenge persists.  

What the customer wanted

Complexity in problem definition, solution and design tool architecture, organizational structures and market forces demand agility and constant risk assessment. According to the Project Management Institute (PMI), of the two in five projects that fail to meet business objectives, half traced the cause of failure to ineffective communications. In software development projects these typically include incomplete or changing requirement specifications, and lack of user input.  

Don’t assume that all project stakeholders have the same understanding of the term “requirements”. A broad ranging definition is: Requirements are a specification of what should be implemented. They are descriptions of how the system should behave, or of a system property or attribute. They may be a constraint on the development process of the system. A non-functional requirement should define how well the system must do what it does.