We get comparison questions a lot: Is it better to learn x or y? Is this language even worth learning over that language? The most recent example: Is Java and Kotlin development dead for Android development? When compared to progressive web apps (PWAs), which while more ‘generalized’, can be faster, and can cross-platform(Android & iOS) so you only have to write the app once, it’s easy to see why native tech would not be long for this world.
Our answer is, “I think native dev is going to be important for awhile…[but] there’s nothing to be lost by learning any language, as I said you can’t lose when you learn – even if you don’t end up using the technology.” “…Because what you’re going to see as you advance as a developer…is that all these frameworks, all these languages share many, many, many, many things in common and in fact when you learn your second framework, when you learn your second and third and fourth language (which will eventually happen), learning the new languages and frameworks are going to make you more knowledgeable of all the frameworks and languages you learn.” So, if you learn Java and then you go into PHP, you’re going to find the PHP is “…pretty much like Java. Yeah there’s some differences here and there but whatever; a function’s a function, a method is a method, and arrays are arrays…”.
Check out the VLOG for a more eloquent explanation of this thinking, but essentially, learn as much as you can because most languages have more in common than different, and you can’t lose from learning. -Enjoy!
…That’s ‘Positive Mental Attitude’ for ‘Progressive Web Apps’…
We keep on getting requests to cover PWA/RWD’s and because we’re not DJs or that small band at the back of the bar that’s playing ‘only originals’, we’re taking those requests…and 5-6-7-8…
So a PWA is a progressive web app and an RWD is a responsive web design. How are the two related? Well first off, “RWD is basically writing your HTML5 and your CSS code so that the layout of the site will flex and change depending on the size of the screen of the web browser that is visiting your site. So if you have a smartphone or a 75 inch flat panel TV, a properly coded responsive website or web app will look just fine.” So the idea being that fonts, images, layout, etc. will change size depending on the size of the screen you’re viewing them on. As you can imagine, with the way consume data and media, it was a pretty big deal.
Okay, but where does the PWA come in? “…A PWA is basically taking RWD to its ultimate highest level. Essentially…you can think of it as RWD on steroids, because it brings in all the power that comes with native HTML5 and CSS (and you throw in some JavaScript to add some extra capabilities, of course…).” “The big advantage of using a PWA over native is you have one code base, so instead of having to write one app in iOS with SWIFT, and then having to write the whole app again from scratch for android in JAVA or KOTLIN. PWA is a lot cheaper to get your app out there, and [while] you don’t get the full benefit with a PWA that you get with native, you get a lot of the benefits.”
Now the VLOG will go into really good detail weighing the pros and cons of PWA or native (and believe me there are way more pros), but as a dev or a freelancer you should always be thinking about where businesses are coming from. Most of the time they’re not interested in the “nerd” implications of the languages, frameworks, etc. that you use, they just want to get up and running fast and get the product or service out there and PWA is your best bet. -ENJOY
