CategoryPWA

February 9, 2018 — Deciding to build a PWA or a native app should be based on the needs of the specific project, not hype. In this article, Aaron Gustafson walks you through the pros and cons of each approach to help you arrive at an informed decision. Read more…

November 27, 2017 — Users couldn’t care less about whether a technology is native, an installed web app or a website. What makes users engage and makes shoppers convert is really the experience itself. In this article, Mitch takes a closer look at PWAs on Android devices and explains how we can pave the way for a new era of browserless web browsing. Read more…

May 29, 2017 — For the holidays, the owner of (and my boss at) thirteen23 gave each employee a Google Home device. If you don’t already know, Google Home is a voice-activated speaker powered by Google Assistant and is a competing product to Amazon’s line of Alexa products. I already have the Amazon Echo, and as Director of Technology at thirteen23, I love tinkering with software for new products. For the Amazon Echo, you can create what are called “skills”, which allow you to build custom interactions when speaking to the device. Read more…

December 8, 2016 — Even though the new Service Worker API allows you to cache away all of your website’s assets for an almost instant subsequent load, like when meeting someone new, the first impression is what counts. If the first load takes more than 3 seconds, the latest DoubleClick study shows that more than 53% of all users will drop off. Read more…

September 5, 2016 — The common wisdom for most companies that set out to build an app is to build a native Android or iOS app, as well as a supporting website. Although there are some good reasons for that, not enough people know about the major advantages of web apps. Read more…