__________     __ __     __  _______    ________
  / ____/ __ \   / // /    / / / /  _/ |  / / ____/
 / / __/ / / /  / // /_   / /_/ // / | | / / __/
/ /_/ / /_/ /  /__  __/  / __  // /  | |/ / /___
\____/\____/     /_/    /_/ /_/___/  |___/_____/

 --- A GOPHER-LIKE INTERFACE FOR HIVE BLOCKCHAIN ---

A Simple Guide To Native Mobile Technologies

BY: @wiredelta | CREATED: April 2, 2019, 10:58 a.m. | VOTES: 1 | PAYOUT: $0.00 | [ VOTE ]

[IMAGE: https://cdn.steemitimages.com/DQmVAg3Bad7Gvp4xCZ69gQUt6k89KQJxkuerLwpRUevYnao/image.png]

Have you ever wondered what the difference between hybrid and native technologies is? Well, simply said Hybrid technologies are web applications "wrapped" in code. In other words, they use custom built APIs that communicate with web technologies like HTML, CSS and JavaScript libraries. On the other hand, native technologies use native APIs that are built specifically for each platform. They are developed in programming languages such as Java and C++.

In theory, it doesn't sound that complicated. But when it comes to the actual selection between those two for your project, things get complicated. That's when we come in. Should you go hybrid or native? That's one of the things we help clarify in this article.

TAGS: [ #programming ] [ #development ] [ #backend ] [ #frontend ] [ #mobile ]

Replies

NO REPLIES FOUND.

[ BACK TO TRENDING ] [ BACK TO MENU ]
CMD>