Red Hawk Technologies Mobile App Configurator

Based on your responses, it appears that a Hybrid Mobile Application is the best approach for your project. Hybrid Mobile Apps are built using a combination of web technologies like HTML, CSS, and JavaScript. Hybrid applications are hosted inside a native app and utilize the mobile platform’s WebView. It’s nearly impossible to tell the difference between a well-built Hybrid Mobile App and a Native Mobile App. The primary benefit is that you can expect to repurpose about 80 percent or more of the source code across multiple operating systems. A white paper, detailing technical limitations and the pros and cons of each approach, will be included with your download. Based on your responses, it appears that a Native Mobile Application is the best approach for your project. A Native Mobile Application is a smartphone application that is coded in a specific programming language. Developers will program the native application in Objective C for iOS, Java for Android and C# for Universal Windows Platform (UWP) supported by Windows 10. No code is repurposed when producing the same application for multiple operating systems. The primary benefit of this approach is that you are “closer to the metal.” This is the phrase we like to use at Red Hawk. It means the app will perform very fast when processing complex tasks and you’ll have access to ALL of the device’s sensors, gesture libraries, etc. A white paper, detailing technical limitations and the pros and cons of each approach, will be included with your download. Based on your responses, it appears that an HTML5 Mobile Responsive Web Application is the best approach for your project. An HTML5 Mobile Responsive Web App is built using the same web technologies as the Hybrid Mobile App, but it is not hosted in a native application and it is not distributed through mobile app marketplaces. The standards for mobile browsers are rapidly evolving, allowing developers to control an increasing number of device-specific features through HTML5 coding, including the camera, push notifications, accelerometer, etc. Many of these features were previously unavailable through the mobile browser and would have required a Native or Hybrid Mobile App to control. This is a viable option for businesses that do not intend for their application to be publicly accessible. The primary benefit is that it is supported across all mobile devices and there is only one codebase to maintain, significantly reducing the cost of ownership. There are limitations with this approach. A white paper, detailing technical limitations and the pros and cons of each approach, will be included with your download.

Labs

Mobile App Configurator

Native

Hybrid

Web App

Will you need help with your application?

Your decision disqualified the HTML5 Web App

	YES. I want the general public to discover the app. It’s critical to our marketing strategy.
	NO. I want to distribute the application to a limited set of users.

	HIGH. My app is going to be complex, like a video game.
	MEDIUM. My app is going to have a fairly simple interface and might include basic animation.
	LOW. There will be some basic calculations that will rely on the device CPU.

	FREQUENTLY. We’ll add features and content regularly.
	INFREQUENTLY. We might want to add features at somepoint.
	RARELY. We’ll just maintain the application so it works when operating system(s) upgrade.

	ONE. (iOS, Android or Windows)
	TWO OR MORE OPERATING SYSTEMS.

	HIGH. ($150k to $500k)
	MEDIUM. ($75k to $150k)
	LOW. ($25k to $75k)

	HIGH. ($50k+)
	MEDIUM. ($20k+)
	LOW. ($5k+)