Mobile Apps

What's on offer

  • Apps

    Platforms and app approaches supported

    • iOS and Android
    • Native Mobile App
    • Hybrid Mobile Apps
    • Web (HTML 5.0) Mobile Apps

    Our core technical skills

    • SWIFT, Objective C, JAVA, .Net, C#, Cordova, PhoneGap, Bootstrap
    • HTML 5.0, CSS, JavaScript, AngularJS, Angular Material, JQuery, JQueryMobile
  • Are mobile apps different?

    Yes, code is specifically designed to be used on phones, tablets and wearables. As such there are considerations unique to mobility.

    Significant focus is required on design compliance, usability, performance, screen form factor, input control, memory use and battery life.

    As each platform differs in this respect, it makes releasing a good quality App across multiple devices challenging.

    You have to: –

    • Consider which platforms to support.
    • Decide to design separately or not for phone, tablet and wearable.
    • Choose an APp approach that best suits your need and budget.

Which approach?

There is no exact science to which approach best suits your need, and there are many competing opinions and cost, effort and time factors to consider. To help your decision process we have summarised the App approaches with example use.

  • Native Mobile Apps

    Apps are built in the language supported by the platform that the device runs on.

    This is the approach the platform and device providers prefer as you code within their environment.


    WhatsApp – to achieve the ease of use, speed, performance and reliability in the millions of messages sent daily they have created a native App for iPhone (iOS), Android, Windows Phone and BlackBerry.

    • Users prefer native apps
    • Best UI experience
    • All features of device available
    • Best performance and memory use

    • Each platform coded separately
    • Design has to be adapted to each platform

  • Hybrid Mobile Apps

    Apps are built “mostly” in one language and then compiled onto each platform required.

    Note that in most cases it is still necessary to code and configure as per Native Mobile Apps for the user interface and deployment configuration.


    A large organisation who has a BYO policy on mobile devices and wishes to provide mobile applications for staff use.

    • Allows leverage of existing skills in one language
    • Allows for code-reuse across platforms
    • Speeds up deployment

    • Only suits certain types of Apps
    • Apps end up bloated and can perform badly
    • Being a hybrid approach can bring out the worst rather than the best of the approaches used
  • Web-based Mobile Apps

    Apps are built using HTML 5.0 and supporting technologies that allow access to each platforms functionality.

    To use the App on the device a browser must be used either standalone or wrapped in a Native Mobile App wrapper.


    Many media organisations use this approach, each platform has a Native Mobile App which is in effect a wrapper App, then all functionality and content is provided via HTML 5.0.

    • Allows a significant amount of code to be in HTML 5.0
    • The code in HTML 5.0 can be used for PCs
    • Limits the Native Mobile App coding to a minimum or none at all if provided through a standalone browser.

    • Requires a browser to work
    • UI experience can be limited
    • Interaction can lag

Our solution expertise

We have extensive experience across all App approaches and currently we support iOS (Apple) and Android Phone App development. We support both App Store and enterprise deployment and have considerable experience in ensuring a smooth passage through each App Store certification and testing process.

Return to App Development page to view examples of our work and client testimonials.

Back to App Development