<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Michał Szklarski on Medium]]></title>
        <description><![CDATA[Stories by Michał Szklarski on Medium]]></description>
        <link>https://medium.com/@mszklarski?source=rss-aba978a21715------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*4V1MKhZQGPo4vnUknOZasA.jpeg</url>
            <title>Stories by Michał Szklarski on Medium</title>
            <link>https://medium.com/@mszklarski?source=rss-aba978a21715------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 11:17:59 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mszklarski/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[80% increase in ticket sales thanks to website upgrade to PWA [case study]]]></title>
            <link>https://medium.com/@mszklarski/80-increase-in-ticket-sales-thanks-to-website-upgrade-to-pwa-case-study-e1040ff0b863?source=rss-aba978a21715------2</link>
            <guid isPermaLink="false">https://medium.com/p/e1040ff0b863</guid>
            <category><![CDATA[business]]></category>
            <category><![CDATA[cinema]]></category>
            <category><![CDATA[pwa]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[entertainment]]></category>
            <dc:creator><![CDATA[Michał Szklarski]]></dc:creator>
            <pubDate>Fri, 17 May 2019 13:57:20 GMT</pubDate>
            <atom:updated>2019-05-17T13:57:20.332Z</atom:updated>
            <content:encoded><![CDATA[<p>New studies show cinema-goers are ever more frequently using their smartphones to see what’s playing and buy tickets. Why? Because it’s convenient. People can pick a movie and book tickets wherever and whenever they want over a device that’s always at their side.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-efUc8i147b3AcJe" /><figcaption>Smartphones nowadays — in every pocket</figcaption></figure><p>This implies spontaneity is playing an increasing role in purchases, but there is a snag in it too. If it takes too long to find information or complete checkout, customers get frustrated and abandon their purchases.</p><h3>Optimized Mobile Experience for Cinema Goers</h3><p>For this reason cinema chains and ticket agencies are now trying to deliver an optimal mobile experience that allows customers to:</p><ul><li>choose movies</li><li>check rankings &amp; reviews</li><li>pick the closest cinema for the desired hour</li><li>select seats</li><li>show the number of tickets to be purchased</li><li>take advantage of discounts</li><li>purchase tickets</li><li>get receipts</li><li>add the event to participants’ calendars</li><li>inform family &amp; friends of details</li><li>contact customer service in case of any issues</li></ul><p>It’s also vitally important that even in the case of internet service disruption users can complete the purchase process. Otherwise, they get distracted or lose the desire to buy tickets by the time the internet connection is restored.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/735/0*8yrBWWe0lY_09puc" /><figcaption>Dinosaur @ Google Chrome — synonym for offline</figcaption></figure><h3>Native Mobile App vs. PWA</h3><p>In theory, the native mobile app can be an answer for above requirements. However, this approach is not just very costly, but also ineffective according to recent market data. Cost-wise, it requires cinemas or ticket agencies to pay for custom app development for each mobile operating system, Android and iOS, and then cover ongoing maintenance expenses.</p><p>But downloading app takes too long for the most smartphone users, so they don’t do it. Besides, the app consumes too much precious smartphone memory, and even if they install it, they don’t use it frequently enough. Users prefer to access the cinema’s website via their smartphone browser. For this reason, many cinemas, and leading online retailers from other industries as well are now moving to an alternative solution called PWAs (Progressive Web Applications).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/867/1*FgN79XsoTwaNQ2OtlZ3vuA.png" /><figcaption>PWAs: Design &amp; Implement Once, Run Anywhere</figcaption></figure><p>This technology combines the best features of a native mobile app and a website. It opens via the smartphone browser just like a traditional website, and then behaves just like a native mobile application: featuring functionalities like gesture navigation, cameras, geolocation and push messaging. Plus it works offline AND requires almost no downloading or local memory. For industry leaders who’ve moved to PWAs, the migration has revolutionized their online business.</p><h3>Case Study: BookMyShow</h3><p>BookMyShow, a leading Indian ticket agency, observed that 85% of website transactions were first being attempted via mobile devices. At the same time, the major share of them was abandoned due to slow processing or another website/smartphone problem.</p><p>To solve this problem, the company invested in a custom mobile app. And to their dismay, the native app was hardly used. Customers who did download it either complained about the amount of smartphone memory needed or just uninstalled it. Faced with this fact, the BookMyShow realized they needed to sell tickets the way customers wanted to buy - directly from their website, quickly and easily, via smartphone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/828/1*ReDym_Vd4BFx-w-h2QJhUw.png" /><figcaption>PWA experience on new BookMyShow</figcaption></figure><p>The company decided to upgrade its existing website to a PWA, paying particular attention to system response time and ease of use. Results?</p><ul><li>The entire book and purchase check-out process were reduced down to 30 seconds</li><li>Prior memory issue became non-existing, because the PWA required only 440 KB of space — 54 times less than the BookMyShow Android app and 108 times less than the iOS version</li><li>Load time for particular pages was also highly optimised</li></ul><p><strong>Thanks to these changes, BookMyShow’s online conversion rate increased by 80%!</strong></p><p>The BookMyShow example serves both as an inspiration and valuable lesson for all retailers for whom online sales constitute a vital part of their business. It tells us that today customers simply won’t accept a poor mobile experience: they insist on using smartphones for online shopping and demand that the process be immediate and smooth. Period.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e1040ff0b863" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[PWA FAQ: 14 most common questions about Progressive Web Apps answered]]></title>
            <link>https://medium.com/@mszklarski/pwa-faq-14-most-common-questions-about-progressive-web-apps-answered-d6af075910b0?source=rss-aba978a21715------2</link>
            <guid isPermaLink="false">https://medium.com/p/d6af075910b0</guid>
            <category><![CDATA[pwa]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[faq]]></category>
            <dc:creator><![CDATA[Michał Szklarski]]></dc:creator>
            <pubDate>Mon, 13 May 2019 16:03:00 GMT</pubDate>
            <atom:updated>2019-05-17T08:59:34.949Z</atom:updated>
            <content:encoded><![CDATA[<p>With more and more buzz around Progressive Web Applications, it might be tricky to sort out what it actually means, how it works and whether it can benefit your business. That’s why I decided to share with you the most common questions our clients ask about PWA.</p><h3>1. What is a PWA?</h3><p>PWA or <a href="https://www.e-point.com/what-we-do/pwa">Progressive Web Application</a> is an app written in a web language (JavaScript + frameworks) that works as a native mobile or desktop application.</p><p>It holds a lot of mobile app features, such as:</p><ul><li>push notifications</li><li>ability to work offline and in the background</li><li>use of camera, geolocation or gesture navigation</li><li>and many, many more: as <a href="http://whatwebcando.today/">whatwebcando.today</a> says on your current device — that’s Progressiveness in PWA.</li></ul><p>Yet, contrary to the traditional mobile app, you don’t have to download it. You can simply use it via a browser.</p><h3>2. What difference does PWA make for end users?</h3><p>From a user’s perspective, the application written in PWA combines the best of both worlds: mobile browser and mobile app. It allows easy access directly from the search engine and doesn’t require any additional installation steps — as if you were accessing a website via the browser on your mobile device. But at the same time, it’s optimised for mobile devices. It enables you to use the native functions of the smartphones and tablets, such as push notifications, gesture navigation, camera, QR / bar codes, geolocation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FMNZkpEetROVxxtdJOvvaw.png" /><figcaption>Best of both worlds: mobile app and responsive web</figcaption></figure><p>Thanks to that, you can browse content conveniently, search for information or buy on a mobile device without the necessity of installing a dedicated app. And if you add PWA to the home screen of your device, it will take up much less space than a traditional mobile application.</p><p>It all translates into a better mobile experience.</p><h3>3. Which browsers support PWA?</h3><p>All modern mobile and desktop internet browsers, support both the technologies used to build the PWA and the standard itself.</p><p>Check out <a href="https://caniuse.com/#feat=serviceworkers">support of service workers</a>, main underlying mechanism of PWAs.</p><h3>4. Will PWA work properly on any mobile device?</h3><p>Yes! If your site meets the requirements of the PWA Checklist and passes Google Lighthouse benchmark, all users on any device will benefit from PWA.</p><p>The only exception is devices with outdated versions of mobile operating systems that do not support latest browsers.</p><h3>Chrome Developers on Twitter</h3><p>📱🖥Progressive Web Apps: now universally installable in ... ➡️Chrome on Android ➡️Chrome OS ➡️Windows ➡️Linux ➡️macOS 🎉 #io19</p><h3>5. Is PWA just another technological buzzword?</h3><p>Definitely not! Why? Because the way we use mobile devices has changed dramatically and irreversibly.</p><p>We download fewer applications that we used to and use only a few regularly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/680/0*aznrgdYkCiAEnet0" /></figure><p>At the same time, we browse a lot of online content on our smartphones and expect the experience to be convenient and frictionless — even if without a dedicated application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*2zo3RCjsrA7xlBV9" /></figure><p>Whatsmore, let’s remember that PWA isn’t a novelty. Technologies used to create progressive applications have been around for several years and are actively developed by technological giants: Facebook and Google.</p><p>You can find more examples in our ebook: <a href="https://www.e-point.com/reports/ebook-pwa">PWA in practice: 11 case studies</a></p><h3>6. How long will the implementation take?</h3><p>The average PWA implementation project takes about 3 or 4 months, but a lot depends on the specifics of a given website or e-commerce.</p><p>To optimize the process, consider ready-to-use applications, like the e-point’s <a href="https://www.e-point.com/what-we-do/pwa-commerce-accelerator">PWA Commerce Accelerator</a>, which is very likely to reduce that time even up to few weeks.</p><h3>7. Who needs PWA most?</h3><p>This is a difficult question because due to increasing mobile traffic and user behavior trends mentioned above, PWA will be beneficial to every type of business and every industry, from FMCG to news portals.</p><p>Most advantages, however, will be visible when online sales are involved, both in B2B and B2C because PWA supports customer’s omnichannel journey.</p><p>PWA can also move customer service to the next level: we can keep the customer up to date with invoices to be paid, orders to receive, etc. by using push notifications directly from the browser. Additionally, PWA means a cohesive customer experience (CX) on all devices.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F9FuevuxH4yM%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D9FuevuxH4yM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F9FuevuxH4yM%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/d80739bcc1422748c2818c6b6cc2ddac/href">https://medium.com/media/d80739bcc1422748c2818c6b6cc2ddac/href</a></iframe><h3>8. Why should you implement PWA?</h3><p>The key benefits of PWA implementation are:</p><ul><li>Lowering the costs (1 team and 1 technology instead of separate units for browsers and mobile applications for each platform)</li><li>Increasing visibility in search engines (read more on that below)</li><li>Improving page performance</li><li>Improving the effectiveness of new users acquisition (letting people just find your website via browser is much easier than encouraging them to download your app)</li><li>Higher user engagement, which translates into an increase in conversion and decrease of the bounce rate</li><li>Avoiding problems related to mobile applications (long deployment and update times, the necessity of downloading through a dedicated store app, Apple / Google verification)</li><li>Possibility of integration with any existing (or new) system operating as a data source — back-end</li></ul><h3>9. What are the best examples of PWAs?</h3><p>There are a lot of inspirational examples in various industries. You can find a lot of inspiring case studies on Google Developer page <a href="https://developers.google.com/web/showcase/">https://developers.google.com/web/showcase/</a></p><p>My favourites examples are:</p><ul><li>Forbes. Speed matters! New Forbes page loads in 0.8 seconds! Introducing PWA has triggered mobile users to browse the site for a longer time and look at more content. Thus, they watch more ads. For Forbes it means not only providing better quality to its readers but also offering more to advertisers</li><li>Trivago. Up to half a million people have added PWA Trivago to their home screens. They are much more engaged, and the conversion has increased by 97%</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9vXd_tP6WNiPt-Xe" /><figcaption>Trivago Case Study</figcaption></figure><h3>10. Who should you invite to PWA implementation project?</h3><p>The implementation of a website compliant with the PWA standard requires similar personnel as front-end projects. So the team should include:</p><ul><li>Front-end Developers (JavaScript, HTML, CSS, frameworks)</li><li>Full-stack Developers (JavaScript, frameworks)</li><li>UX experts</li><li>Project Managers</li></ul><h3>11. Where to begin?</h3><p>So, you see how your business could benefit from introducing PWA and improving users’ mobile experience. What now? How to start?</p><ol><li>Diagnose the current condition of the website and analyse users’ feedback. To do so, use for example Google Lighthouse.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2tSHvEQboUwdPZnj" /><figcaption>Lighthouse auditing tool</figcaption></figure><ol><li>List the benefits you want to achieve with PWA or challenges that PWA has to address. Make your aims clear.</li><li>Gather knowledge about the current technological and information architecture</li><li>Make sure that there is a clear boundary between what the front of the site is responsible for, and what the tasks of the back-end systems are</li><li>Choose the best implementation option. Do you want to (1) just refresh the current version of the portal or platform, adapting it to the PWA standard? Or maybe you prefer to (2) use a ready solution (like PWA Commerce Accelerator), or (3) do the entire front of the site from scratch.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZjleY-knn_6XYCCIkSt0XQ.png" /><figcaption>Implementing PWA: strategies</figcaption></figure><p>These decisions and information are the foundation of success in implementing PWA.</p><h3>12. Does PWA support SEO?</h3><p>Contrary to the popular myth, just implementing PWA won’t ensure better positioning of the website in search engines. But if you meet the checklist requirements and stick to all points, without any omissions or simplifications, your web application will be higher in the ranking than others that do not follow these assumptions.</p><h3>13. Vue or React: which technology to choose?</h3><p>It depends on the scale of the business.</p><ul><li>Vue.js is a remarkable set of tools (framework) for smaller projects because it’s focused on functional simplicity. The only problem is, however, that it doesn’t have any support from bigger companies which would undoubtedly ensure stability in the dynamic world of JavaScript technology.</li><li>React.js has Facebook backing as well as a broad community supporting it.</li></ul><p>At e-point, we chose React.js technology because of the access to information, greater control over the architecture of projects (React does not impose any specific requirements, as opposed to Angular), better adjustment to the enterprise sector due to efficiency, stability and security and good quality of accompanying libraries (Redux, React Router, Next.js).</p><h3>14. Are there solutions dedicated to specific e-commerce platforms?</h3><p>In the PHP world, there are several similar solutions. Nevertheless, for systems and services located in a stable and secure Java ecosystem, <a href="https://www.e-point.com/what-we-do/pwa-commerce-accelerator">PWA Commerce Accelerator</a> by e-point is the first dedicated solution.</p><p>Do you have more questions about PWA? Feel free to ask me!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d6af075910b0" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>