a

So You’re Thinking About Having Your IT Team Do Mobile App Development?

Joel Garcia Joel Garcia has been building AllCode since 2015. He’s an innovative, hands-on executive with a proven record of designing, developing, and operating Software-as-a-Service (SaaS), mobile, and desktop solutions. Joel has expertise in HealthTech, VoIP, and cloud-based solutions. Joel has experience scaling multiple start-ups for successful exits to IMS Health and Golden Gate Capital, […]

Your company requires a mobile app. You’ve evaluated potential vendors.  The CFO asks the IT team ,who has no mobile experience, to investigate building the mobile app internally.
Here are some items that you will want to consider:

  1. Do not build a hybrid mobile app solution. You will want to go native iOS and Android. If you build a hybrid mobile solution using HTML5 and PhoneGap, you will regret it. Whenever a new version of Android or iOS comes out, any third party packages that you use will break. Typically, the third party packages are written by open source developers who may or may not release an update. Don’t get screwed. Go native.
  2. Mobile Designer - You’ll need to find someone to design your iOS and Android apps. Typically, they’re a little different. Android will be Material Design.
  3. Android - Requires Java and Android Studio expertise.
  4. iOS - Requires Objective C, Swift and Xcode expertise.
  5. Working in offline mode - You’ll want to make sure that the mobile apps work when the internet isn’t available. Typically, this means storing the data in SQLLite.
  6. Analytics - You will want to know who is using your apps, and when people are getting stuck in the app. We typically leverage Google Tag Manager for this.
  7. Test App Distribution - Before putting your app into the store, you’ll want to distribute the app to internal testers. This can be painful. We recommend Crashlytics.
  8. Test and Production Environments - You will need to maintain different cloud environments for your apps.
  9. Apple Developer Program - You’ll need to signup. This takes time to get approved.
  10. Android Developer Program - This is easy
  11. The initial version of your iOS app will most likely get rejected. You will need to submit it a few times. I’d budget two to four weeks to get the iOS app into the App Store.
  12. You will need to design marketing images for the App Store and Google Play.

trove mobile app development trove mobile app development

Good Luck!

Joel Garcia
Joel Garcia

Joel Garcia has been building AllCode since 2015. He’s an innovative, hands-on executive with a proven record of designing, developing, and operating Software-as-a-Service (SaaS), mobile, and desktop solutions. Joel has expertise in HealthTech, VoIP, and cloud-based solutions. Joel has experience scaling multiple start-ups for successful exits to IMS Health and Golden Gate Capital, as well as working at mature, industry-leading software companies. He’s held executive engineering positions in San Francisco at TidalWave, LittleCast, Self Health Network, LiveVox acquired by Golden Gate Capital, and Med-Vantage acquired by IMS Health.

Related Articles

The Difference Between Amazon RDS and Aurora

The Difference Between Amazon RDS and Aurora

AWS does incorporate several database services that offer high performance and great functionality. However, customers do find the difference between Amazon Relational Database Service and Amazon Aurora. Both services do provide similar functions, but do cover their own use cases.

AWS Snowflake Data Warehouse Pricing Guide

AWS Snowflake Data Warehouse Pricing Guide

AWS Snowflake Data Warehouse – or just Snowflake – is a data cloud built for users to mobilize, centralize, and process large quantities of data. Regardless of how many sources are connected to Snowflake or the user’s preferred type of organized data used, data is easily stored and controllably shared with selectively-authorized access. Snowflake does offer extensive control over its pricing, though how it works isn’t always clear.

Single-Tenant vs. Multi-Tenant Cloud Environments

Single-Tenant vs. Multi-Tenant Cloud Environments

Operating a cloud environment and optimizing Software as a Service can be managed in two different methods. Reasons for adopting either single-tenant or multi-tenant cloud environments are dependent on business and customer-related factors as well as how much more expensive one architectural structure will be over the other. Both structure types also have a number of security and privacy implications tied to their inherent design.

Download our 10-Step Cloud Migration ChecklistYou'll get direct access to our full-length guide on Google Docs. From here, you will be able to make a copy, download the content, and share it with your team.