Categories androidApp StoreAppleAppsGoogleInformationInnovationiOSiPadiPhoneMobilenew techSmartphoneTechTrend

Mobile Frameworks vs Web Frameworks

Ever since … well… don’t know when exactly this started but our lives have been flooded with all the distractions from mobile apps because … we love our smartphones. Also, those apps are just incredibly convenient for us to get our jobs done or to get our needs served in unbelievably efficient ways. So … ever since … again… don’t know when exactly this started but every single company (even small clothing stores located on the corner of the street you live) wants to (and maybe has to) have its own mobile app on whatever needs they want to serve. So … how do they do that? The mobile development is time-consuming and costly so … how can they afford to do so?


Here Comes Mobile Frameworks (Hybrid Mobile Apps Developments)

As the technology advanced, there are multiple mobile frameworks (so called hybrid developments) popping up every so often. The most popular one (still) on the market so far is – “ionic mobile framework”. Essentially it uses web technologies to implement mobile developments. There are pros and cons but … it addresses the major challenges and lower the thresholds of getting into the mobile apps world. Mobile frameworks shortened the development time; therefore, it cost the costs to … well… way below half of the cost if you go for the native development.

Hybrid Mobile Development Popping Up Everywhere

Mobile Frameworks – Use Web Technologies To Do Mobile Works

Web Technologies Apply on Mobile Devices

We don’t need to be an expert to sense that there might be some issues. Sure, it can create mobile apps in a shorter time frame compared with developing via native approach. It can also get us both android and iOS apps at the same time since … it’s via webview to get everything implemented… meaning that you aren’t really interacting on the mobile components. Instead, you are doing everything right on the webview (e.g., browser interface UI components). The performance isn’t as good as the native mobile app. In addition, there are lots of obstacles when developing the mobile apps using mobile frameworks since you might need to control device hardwares such as camera, gps, and physical buttons …etc. If you are a developer, once a bug or situation occurs… that might haunt you days or even weeks to get that specific problem solved. If the problem is related to the sudden mobile OS version upgrade, you probably won’t be able to get out of the muddy ground until your chosen mobile framework team solves that issue and update the framework.

Why is the life this difficult on the mobile framework side? Because… it uses WEB technology on MOBILE devices.


Web Frameworks Serves Different Purposes Compared With Mobile Frameworks

When talking about frameworks, some people might wonder why web frameworks work on web developments but mobile frameworks don’t really work well on mobile developments (we are talking about challenges and performance wises scenarios)? The major difference is that “Mobile frameworks use WEB technology onto Mobile devices“; however, “Web frameworks use WEB technology onto WEB inventions“. Meaning that “Web frameworks” only make developers lives easier by combining necessary and useful packages/tools/utilities/functions (whatever you wanna call) together to speed up the development cycle. They don’t do some odd twists to make things happen. However, the mobile frameworks cannot do that since they have to render everything through webview instead of native mobile components; therefore, performance suffers, peculiar behaviors happen, and some implementations that you would like to have might not be possible (yet) due to the restrictions of the webview technology.


“Web frameworks” only make developers lives easier by combining necessary and useful packages/tools/utilities/functions (whatever you wanna call) together to speed up the development cycle.


So … Which One Should You Choose?

Honestly, if you aren’t a mobile company … or in general, you don’t need to utilize native components that much (e.g., retailers… sell & buy industries), hybrid should serve your purpose well. It will drastically reduce the cost of getting your own mobile apps (in both android and iOS) up and running. In addition, the performance won’t damp your company’s reputation since … first, you don’t interact with devices directly that much… second, the hardware of smartphones advanced a lot in the recently years. The poor performance issue isn’t an issue anymore on most of the recent smartphones because … they are just too powerful these days.

However, if you are a mobile company… (well… if you are … you would have been all set already … so …)… let’s say a gaming startup, you would definitely choose native approach for sue without a doubt. In fact, you won’t be reading this article at all since you know exactly what you need to get things done in a right way in your domain.


Happy Mobile Tech Advancing, folks~~~! 🙂