Several years ago, I considered whether I should make the jump from producing apps for the web to iphone or android. I decided to stick with web apps for a few reasons, and I’m glad I did.
- Web apps are ubiquitous. A browser can run on virtually any platform, so an app made for a browser (web app), will have greater reach.
- I’m betting on the internet. As popular as phone or desktop OS’s are, I’m willing to bet that the internet will be more popular and especially more universal now and into the futur.
- We can wrap a web app natively anyway. The power of a browser, and therefore web apps, has gotten to the point that they can be easily wrapped and ported to a native system like macOS or Windows. Why write the code 3 separate times when you can write it once and have it shipped natively and on the web with the same code? This saves you time and money.
Preferred weapons of choice
Most of our apps are built with the following tools, frameworks & languages:
Oakparks is our biggest maintained web app. It’s the web’s largest database and runs off of its own RESTful JSON API. It was built with Laravel (PHP, SQL, nginx) and includes several adaptable web crawlers, data normalization classes, and performance optimization techniques to work with a database of several million entries.
Online Hearing Test is a ReactJS app to thoroughly and accurately test user’s hearing. Its frontend is entirely built in React, uses the redux approach to global state, connects to other web services such as Amazon SES for email notifications, and connects directly to Salesforce to save its data.