<?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 Cristian Olaru on Medium]]></title>
        <description><![CDATA[Stories by Cristian Olaru on Medium]]></description>
        <link>https://medium.com/@colaru?source=rss-91f1357cf9e5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*lDnWCJ-E7LdY4yeORELxjg.jpeg</url>
            <title>Stories by Cristian Olaru on Medium</title>
            <link>https://medium.com/@colaru?source=rss-91f1357cf9e5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 11:59:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@colaru/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[An introduction to the NOSTR protocol]]></title>
            <link>https://medium.com/@colaru/an-introduction-to-nostr-protocol-dbc774ac797c?source=rss-91f1357cf9e5------2</link>
            <guid isPermaLink="false">https://medium.com/p/dbc774ac797c</guid>
            <category><![CDATA[nostr]]></category>
            <category><![CDATA[social-media]]></category>
            <category><![CDATA[twitter]]></category>
            <category><![CDATA[free-speech]]></category>
            <dc:creator><![CDATA[Cristian Olaru]]></dc:creator>
            <pubDate>Sat, 23 Dec 2023 08:24:27 GMT</pubDate>
            <atom:updated>2024-04-27T09:47:53.754Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Nostr’s Mission: Restoring the Promise of the Free and Open Internet</strong></h3><p><em>You can find an introductory video about NOSTR and other information here: </em><a href="https://nostradamic.com/"><em>https://nostradamic.com/</em></a></p><p><strong>George Orwell</strong> said the following words some 50 years, well before the birth of the Internet: “If liberty means anything at all, it means the right to tell people what they do not want to hear.”. Yet, the quote from the author of 1984 (the dystopia where every aspect of society is controlled, which is quite telling) depicts a reality that we confront today<strong>: a digital space where censorship and freedom are infringed.</strong></p><p>Social media has become a double-edged sword. It was initially conceived as a platform for connection, expression, and open communication, a place where people could share their thoughts and experiences with the world. But, over time, it strayed from its original purpose.</p><p>It’s a shift that’s hard to ignore, and it comes with a price: censorship and control. Issues like censorship, data misuse, and centralized control have tarnished the once-ideal vision of social media. How did the ideals of an open digital world become tarnished?</p><p>Intending to steer away from the risks of a digital 1984 in our days, Nostr (short for Notes &amp; Other Stuff Transmitted by Relays<strong>) </strong>actively addresses the challenges that have long burdened traditional networks, reinstating user control and flowing decentralization in a genuinely open and interconnected digital ecosystem:</p><p>1. <strong>Giving the Control Back to the User</strong>: Traditional social media platforms have shifted from their original vision, concentrating power in the hands of a few. Nostr counters this by promoting decentralization, allowing users to regain control of their digital identities, and preventing any single entity from monopolizing information flow.</p><p>2. <strong>Your Choice Matters</strong>: Nostr offers a refreshing change from the one-size-fits-all approach of conventional platforms. Users can select from various Nostr-compatible apps, each providing a unique way to interact with social media.</p><p>3. <strong>No One’s in Control</strong>: Nostr isn’t owned by one big company. It’s open for everyone to use and change, like a big digital playground. No one can decide what you can and can’t see.</p><h3><strong>Social Media — from Total Freedom to Stringent Control</strong></h3><p><em>Connection, communication, and freedom</em> — these pillars represent the foundation of social media that began as a liberating force, a digital utopia where everyone had a voice and the world seemed more connected. It was a space where ideas could flow freely, and users could express themselves without the limits and restrictions we see today.</p><p>Over a decade ago, when platforms like Twitter were born, there was an air of excitement and innovation. These platforms were not just about connecting people; they were about creating an entirely new way of interaction. The Internet’s early days were characterized by open protocols and decentralized structures, allowing for unprecedented innovation and freedom. Protocols functioned like digital highways, transporting data across the globe.</p><p>However, early internet companies grappled with organizing the chaotic sea of data, leading to the birth of giants like Google, Facebook, and Twitter. Initially focusing on managing specific organizational tasks, these companies gradually began centralizing information, shifting away from the Internet’s original decentralized ethos.</p><p>And as these platforms grew, they transformed into something quite different from their original vision. The very essence of social media, once driven by a desire to connect, has become more about retaining users at any cost. Leaders in the digital space initially didn’t realize the full extent of our responsibility in shaping this digital world, and this oversight has led to unforeseen consequences.</p><p><em>How did this change happen? And more importantly, what went wrong?</em></p><p>Now, think about a future where a massive online retailer like MegaMart starts bidding for exclusive rights to manage public transportation systems. They introduce a fleet of smart buses equipped with advanced sensors that collect data on passengers’ travel habits, destinations, and preferences. Then, as cities rush to cut costs, they embrace MegaMart’s transportation solution. In this scenario, people may unwittingly become data sources for MegaMart’s profit, feeling like passengers on a tech-driven transit system serving corporate interests.</p><p>In fact, this example is a tangible representation of Techno-feudalism, explaining how Big Tech ushered in a new economic era. Unlike traditional capitalism, where profits fuelled innovation and productivity, today’s capitalists increasingly thrive on surveillance-based platforms, often distanced from the workers who provide goods and services.</p><p>Within these dynamics, we are not fighting for finite resources but for the “cloud capital,” the driving force of Techno-feudalism. It’s different from the old capitalism that focused on buying and selling goods. Cloud Capitalism is all about controlling and using digital information worldwide, crossing any borders.</p><h3><strong>Understanding the Addiction Model of Social Media</strong></h3><p>Social media isn’t just about sharing anymore; it’s about keeping you hooked. Have you noticed how hard it is to stop scrolling through Instagram or Twitter? That’s not by chance; it’s by design. These platforms have evolved into finely-tuned machines, with algorithms designed to learn what keeps you engaged, showing you more of it and making it nearly impossible to look away.</p><p>More than two billion individuals use Instagram, Twitter, and TikTok daily. Yet, their business ideas are based on user addiction rather than merely user engagement. And this is a deliberate design strategy, not an accident. The online communities we used to be a part of for fun and connection have slowly transformed into mazes that are becoming harder and harder to escape.</p><p>As these platforms grew, they became more than just digital spaces; they became powerhouses of information control. A single entity, often led by just a few individuals, began to decide what millions would see, read, and believe. This power to influence is immense and, quite frankly, frightening. It led to the creation of ‘walled gardens’ — closed ecosystems where platforms had complete control over the content and the user experience.</p><p>Eventually, the centralization of social media has impacted user experience and given rise to issues like censorship and data control. Platforms now have the power to decide what is seen and what is not, a power that can be used against the very users they serve.</p><h3><strong>Nostr Brings Back Control, Choice, &amp; Freedom for the User</strong></h3><p>Battling all of the faults instilled by the rise of Big Tech social media, Nostr represents a new, innovative form of technology for social media. Metaphorically, it resembles an open field where many different apps can access and share the same social media content rather than having one company control everything.</p><p>Nostr empowers users with more control over their social media experiences. It’s a return to the Internet’s original promise: an open, free space for all. Users are no longer confined to one platform’s content presentation and may choose from different apps that connect to Nostr, each offering a unique way of interacting with the same data.</p><p>Users can select an app that aligns with their preferences — be it a text-focused interface resembling Twitter or a visually driven one akin to Instagram. Nostr’s model encourages constant innovation as developers strive to create more user-friendly and engaging platforms. Altogether, the variety ensures that users can find an app that resonates with their personal preferences rather than conforming to the one-size-fits-all approach of traditional social media platforms.</p><h3><strong>The Basics: How Nostr Works</strong></h3><p>Do you know how you can send emails from Gmail, Yahoo, Hotmail, AOL, and other email services to anyone, no matter which service they use? Well, this is possible because they all follow the same rules, or “protocols,” for sending and receiving emails.</p><p>These rules or protocols ensure that different email services can speak to each other, just like speaking the same language. So, even if you have Gmail and your friend has Yahoo, you can still exchange emails because both services use these open protocols.</p><p>Now, imagine the same idea, but for social media. Nostr is like a set of rules (protocols) that allow different social media services to work together. With Nostr, people can create different “clients” or apps, just like Gmail or Yahoo, to send emails. Some Nostr clients work on Twitter, some on Telegram, some on desktop, and some on mobile.</p><p>The significant part is that all these Nostr clients understand the same rules (protocols), just like Gmail and Yahoo understand email protocols. So, even if you’re using a Twitter-like Nostr client, and your friend prefers a Telegram-like one, you can still interact with each other because they follow the same Nostr protocols.</p><p>In other words, you gain the freedom to choose different Nostr clients, and they can all work together. Nostr isn’t a closed or isolated system; it’s open and lets you connect with others, just like email services.</p><h3><strong><em>Introducing Relays</em></strong></h3><p>Nostr works quite differently than traditional social media problems. Instead of one big server in control, think about Nostr as a network of post offices (called relays) spread worldwide.</p><p>Just like how you can send a letter to anyone through any post office, Nostr lets you send messages through these relays. These relays are not owned by one big company (like Twitter or Facebook) but are run by different people all over the globe.</p><p>When you want to send a message on Nostr, your message goes from your device (the client) to one or more of these relays, similar to dropping your letter in multiple mailboxes.</p><p>Afterward, the relay’s job is simply to hold onto your message. When someone wants to see your message, their device asks the relays for messages from you, which deliver your message to them.</p><h3><strong><em>Introducing Clients</em></strong></h3><p>In Nostr, a client is just the app you use to connect to and use the Nostr protocol. Think of it like the Twitter app you use on your phone or the Twitter website you visit to see tweets.</p><p>Because the Nostr protocol is straightforward and adaptable, different clients have their unique ways of using it. Some make it look exactly like Twitter, some focus on showing how important relays are, and some use smart methods to resist censorship without making things complicated for users.</p><p>Since a client is simply a tool to access data from relays, you can use different clients or log into as many as you want. As long as each client is connected to the same relays for data, you’ll see the exact same messages across all your clients.</p><h3><strong><em>Understanding Nostr Identities</em></strong></h3><p>In Nostr, your digital identity is tied to two key elements: your public and private keys.</p><p><strong><em>Public Key = Unique Id</em></strong></p><p>Think of your public key (a unique 77-digit number) like your social media username — it’s visible to everyone on the network. It’s a long number, unique to you, ensuring no one else can pretend to be you.</p><p><strong><em>Private Key = Secret</em></strong></p><p>On the other hand, your private key is more like a password. It’s another unique number that you keep to yourself, ensuring that your communications are secure and genuinely from you.</p><p><strong><em>Handle = Nickname</em></strong></p><p>But there’s more to your identity in Nostr than just these numbers. Apart from these technical identifiers, you also have what’s known as a ‘handle’ in Nostr, just like a nickname or a chosen name that represents you on the network. It’s how you want others to recognize you.</p><p>For instance, someone might be known as ‘Watchful Guardian’ on Nostr, even though it’s not their real name. It’s more like a CB radio handle — a unique identifier that sets you apart. You’re free to choose your handle and communicate without fear of censorship. It’s all about trusting who you want and expressing yourself freely.</p><h3><strong><em>Exploring the Technology behind Nostr</em></strong></h3><p>Quite simply, Nostr acts “<em>as a social layer for the Internet protocol stack. Big Tech companies had to build a proprietary social graph layer within their vertical since a social graph makes (almost) everything information-based better. Nostr pushes out the social graph from the application layer and allows smaller applications to be built on top</em>.” (<a href="https://njump.me/nevent1qqsvpgz5hlkxuvnhvrjpv4pkvess3ahl2a4k0nf9y7g6v53n56d66vclms2lk">NJUMP</a>, 2023)</p><p>In contrast to peer-to-peer (P2P) networks such as torrents, it does not rely on direct data sharing between peers. Nostr’s decentralization ethos does not depend on a central server or conventional P2P methods, enhancing its resilience and also reducing the risk of single points of failure. Cryptographic keys and signatures sustain an environment for tamper-proof and authentic data.</p><p>Also, Nostr is far different from Bitcoin; its approach to data distribution and management is based on event-driven architecture using web sockets and JSON, an approach to decentralization that is different from both the blockchain and traditional P2P models.</p><h3><strong>Instilling the Potential for Change through Open-Source Structure &amp; Decentralisation</strong></h3><p>Data, algorithms, and content distribution are often under the stringent oversight of traditional social media platforms. Nostr’s approach counters this by advancing decentralization and giving users more agency over their online interactions.</p><p>Down this path, Nostr’s commitment to freedom of choice challenges users to break free from the one-size-fits-all approach of traditional social media. It invites them to explore different client applications aligned with their preferences.</p><p>No single person or entity owns Nostr. It’s an open-source protocol, meaning anyone can contribute to and use it. Although individuals can own specific parts of Nostr, like relays or client applications, the network’s decentralized nature ensures that no one can monopolize or control the flow of information. With numerous relays and various clients available, Nostr maintains an open and unrestricted environment.</p><p>Your social media posts and data are not stored on just one platform (like Twitter or Instagram) but are shared across many different apps- this is what Nostr does. It’s like how many email programs can access the same email account.</p><h3><strong>How Nostr Addresses Common Social Media Problems</strong></h3><p><strong>User bans and server shutdowns</strong> pose challenges in many online communities, but here, users can maintain their identity and followers through public keys, even if banned on one relay. Besides, the network updates relay addresses automatically, ensuring a smooth transition when needed.</p><p>Nostr is built to be inherently <strong>censorship-resistant</strong>. Users can freely publish their updates on multiple relays, creating a decentralized ecosystem that stands strong against censorship attempts. Fees act as a deterrent, guaranteeing a server will always be ready to serve your posts.</p><p>To tackle <strong>spam control</strong>, relays have the option to demand payment, authentication, or implement anti-spam measures. Clients can switch to other relays for updates if a relay becomes spam-ridden.</p><p><strong>Data storage</strong> is handled with remarkable efficiency in this network. It thrives with only a few active relays, and newcomers can join without any constraints, reducing overall storage demands compared to similar platforms.</p><p>Managing <strong>heavy content</strong> is straightforward here. Relays can either reject or charge for hosting large amounts of content, preventing the network from becoming overwhelmed. Market forces maintain order, ensuring the distribution of bandwidth-intensive content remains manageable.</p><p>Empowering <strong>user preferences</strong>, clients enjoy full autonomy in customizing how they view posts, whether AI-driven content sorting or the simplicity of chronological order, ensuring a tailored and satisfying user experience.</p><h3><strong>Surpassing the Limits of Social Media</strong></h3><p>In more depth, Nostr’s structure and philosophy fulfill the original vision of Twitter’s early years when it aimed to provide an open application programming interface (API). In simpler terms, it offers what Twitter had initially envisioned but never fully realized — a more open and adaptable system for users and developers.</p><p>Step by step, it overcomes the shortcomings of the previous centralized social media platforms, defined by tightly regulated ecosystems. Its openness and decentralization make it feasible to build novel applications that would have been impossible with the old, centralized system. In turn, Nostr paves the way for innovative and game-changing technical developments, which is quite exciting.</p><p>But, with the potential to become more than just a new standard for social media, Nostr is a versatile solution that has the capacity to replace platforms like Github, which are fundamental for collaborative software development. Even more, it can serve as a resilient “identity and reputation layer” for users, providing a secure and reliable online identity that can be used across various online services.</p><h3><strong>Takeaways</strong></h3><ul><li><strong>Restoring Digital Liberty:</strong> Echoing Orwell’s vision, Nostr is a powerful antidote to the growing digital censorship, embodying the true spirit of liberty in the digital age.</li><li><strong>Reviving Social Media’s Original Vision:</strong> Nostr returns to the essence of social media as a platform for free expression and connection, countering the trend of centralized control and censorship.</li><li><strong>Challenging the Status Quo:</strong> Nostr not only changes how we interact online but also questions the underlying power structures of the digital world, advocating for a more balanced and equitable information ecosystem.</li><li><strong>Empowerment Through Decentralisation:</strong> By decentralizing control, Nostr hands back the power to users, allowing them to shape their digital experience without interference.</li><li><strong>Diverse Platforms, Unified by Nostr:</strong> The flexibility to choose from various Nostr-compatible apps ensures a more personalized and enjoyable social media experience.</li><li><strong>Innovating Beyond Social Media:</strong> Nostr’s potential extends far beyond traditional social media, offering a resilient framework for new applications and digital interactions.</li><li><strong>A New Era of Digital Interaction:</strong> Nostr isn’t just a platform; it’s a movement towards a more open, interconnected digital world where freedom of expression and innovation thrive.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dbc774ac797c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Java Number One in 2019?]]></title>
            <link>https://medium.com/dev-scenius-playground/java-number-one-in-2019-a413f18e83f2?source=rss-91f1357cf9e5------2</link>
            <guid isPermaLink="false">https://medium.com/p/a413f18e83f2</guid>
            <category><![CDATA[ibm]]></category>
            <category><![CDATA[oracle]]></category>
            <category><![CDATA[spring]]></category>
            <category><![CDATA[kotlin]]></category>
            <category><![CDATA[java]]></category>
            <dc:creator><![CDATA[Cristian Olaru]]></dc:creator>
            <pubDate>Sat, 28 Dec 2019 00:00:43 GMT</pubDate>
            <atom:updated>2019-12-28T00:00:43.873Z</atom:updated>
            <content:encoded><![CDATA[<p><strong><em>End of the year! Some facts about Java in 2019! Is it good? Is it bad? Your thoughts?</em></strong></p><p>In 2019 Java is still number one on Tiobe index — <a href="https://www.tiobe.com/tiobe-index](https://www.tiobe.com/tiobe-index/)">https://www.tiobe.com/tiobe-index</a></p><p><strong>Oracle Java One</strong> conference was renamed to <strong>Code One</strong></p><p>“<strong>Android is Kotlin first</strong>” announced by Google. Google will deliver the Android APIs first in Kotlin and after this in Java</p><p><strong>Refactoring 2nd Edition</strong> by Martin Fowler has the samples in JavaScript and not Java, like in the first version of the book</p><p>VMware acquired Pivotal (Spring)</p><p>IBM acquired RedHat (JBoss)</p><p>Java EE is <strong>JAKARTA EE </strong>now out of Oracle garden and in the Eclipse Foundation — <a href="https://jakarta.ee](https://jakarta.ee/)">https://jakarta.ee</a></p><p>Oracle refuses to let the <strong><em>javax</em></strong> package to be used by Jakarta</p><p>September 2019 → <strong>Java 13 </strong>in many distributions: <a href="https://sdkman.io/jdks](https://sdkman.io/jdks)">https://sdkman.io/jdks</a> (but everyone I know is still blocked at Java 8)</p><p>For 2020</p><p>[Oracle Code One](<a href="https://www.oracle.com/code-one/">https://www.oracle.com/code-one/</a>) Is Moving to Las Vegas -&gt; September 21–24, 2020!<br>[Pivortal Spring One](<a href="https://springoneplatform.io/">https://springoneplatform.io/</a>) Will be in Seattle -&gt; September 21–24, 2020!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a413f18e83f2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dev-scenius-playground/java-number-one-in-2019-a413f18e83f2">Java Number One in 2019?</a> was originally published in <a href="https://medium.com/dev-scenius-playground">Dev Scenius Playground</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Firebase support for Ionic/Cordova]]></title>
            <link>https://medium.com/ionic-book/firebase-suport-in-ionic-cordova-5f77365c7d8f?source=rss-91f1357cf9e5------2</link>
            <guid isPermaLink="false">https://medium.com/p/5f77365c7d8f</guid>
            <category><![CDATA[firebase]]></category>
            <category><![CDATA[ionic]]></category>
            <category><![CDATA[google]]></category>
            <dc:creator><![CDATA[Cristian Olaru]]></dc:creator>
            <pubDate>Tue, 19 Jun 2018 07:51:31 GMT</pubDate>
            <atom:updated>2021-03-09T20:08:52.180Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://firebase.google.com/">Firebase</a> is not just a real-time database as it was at the beginning. After being acquired by Google it becomes the facto serverless solution for mobile. It is not just a replacement for the closed Parse.com and its various clones: <a href="http://parseplatform.org/">http://parseplatform.org</a>. It is an ecosystem for creating serverless backends for your mobile applications with a multitude of features: <a href="https://firebase.google.com/products">https://firebase.google.com/products</a>. Some of them are exposed with a Web SDK, but others have just Native SDKs for iOs and Android.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WPirAj-btHd1X3sKliCZVw.png" /></figure><p>The Firebase Native SDKs support in <a href="https://ionicframework.com/">Ionic</a>/<a href="https://cordova.apache.org/">Cordova</a> is not so good as in other mobile frameworks like <a href="https://facebook.github.io/react-native">React Native</a> or <a href="https://www.nativescript.org/">Native Script</a>. And, Firebase Web SDK is not covering all the functionalities (for example there is no Web support for Analytics — <a href="https://firebase.google.com/docs/analytics/">https://firebase.google.com/docs/analytics/</a> or Remote Config — <a href="https://firebase.google.com/docs/remote-config/">https://firebase.google.com/docs/remote-config/</a>).</p><p>In React Native we have excellent support: RNFirebase <a href="https://rnfirebase.io/docs/v4.2.x/getting-started">https://rnfirebase.io/docs/v4.2.x/getting-started</a><br>In Native Script we have nativescript-plugin-firebase — <a href="https://github.com/EddyVerbruggen/nativescript-plugin-firebase">https://github.com/EddyVerbruggen/nativescript-plugin-firebase</a> (it has even ML Kit support inside)</p><p>In Cordova we have a series of different plugins, each specific to one feature of the Firebase ecosystem — <a href="https://firebase.google.com/products">https://firebase.google.com/products</a> (some of them are integrated into Ionic Native — <a href="https://ionicframework.com/docs/native">https://ionicframework.com/docs/native</a>) :<br>1. cordova-plugin-firebase — <a href="https://github.com/arnesson/cordova-plugin-firebase">https://github.com/arnesson/cordova-plugin-firebase</a> (the most complete plugin with support for Cloud Messaging, Remote Config, Analytics)<br>2. Firebase Analytics — <a href="https://ionicframework.com/docs/native/firebase-analytics/">https://ionicframework.com/docs/native/firebase-analytics/</a><br>3. Firebase Config — <a href="https://ionicframework.com/docs/native/firebase-config/">https://ionicframework.com/docs/native/firebase-config/</a><br>4. Firebase Dynamic Links — <a href="https://ionicframework.com/docs/native/firebase-dynamic-links/">https://ionicframework.com/docs/native/firebase-dynamic-links/</a><br>5. Firebase Messaging — <a href="https://ionicframework.com/docs/native/firebase-messaging/">https://ionicframework.com/docs/native/firebase-messaging/</a><br>6. FCM — <a href="https://ionicframework.com/docs/native/fcm/">https://ionicframework.com/docs/native/fcm/</a></p><p>7. Authentication — <a href="https://github.com/chemerisuk/cordova-plugin-firebase-authentication">https://github.com/chemerisuk/cordova-plugin-firebase-authentication</a></p><p>The problem with this multitude of Cordova plugins is the lack of integration — we will always have issues with the Google Play Services library used on Android, and we will be forced to use other plugins like cordova-android-play-services-gradle-release — <a href="https://github.com/dpa99c/cordova-android-play-services-gradle-release">https://github.com/dpa99c/cordova-android-play-services-gradle-release</a>, cordova-android-firebase-gradle-release — <a href="https://github.com/dpa99c/cordova-android-firebase-gradle-release">https://github.com/dpa99c/cordova-android-firebase-gradle-release</a></p><p>Also, there is no support in Ionic/Cordova for Firebase AdMob, Crashlytics, Performance Monitoring, App Indexing, ML Kit.</p><pre>You can <a href="https://twitter.com/colaru">follow me on Twitter</a> where I continue to document my next steps.</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5f77365c7d8f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ionic-book/firebase-suport-in-ionic-cordova-5f77365c7d8f">Firebase support for Ionic/Cordova</a> was originally published in <a href="https://medium.com/ionic-book">Web Native</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Web Components — How we created a Web component with Stencil JS]]></title>
            <link>https://medium.com/ionic-book/web-components-how-to-create-a-component-with-stencil-3753c20b1b12?source=rss-91f1357cf9e5------2</link>
            <guid isPermaLink="false">https://medium.com/p/3753c20b1b12</guid>
            <category><![CDATA[polymer]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[web-components]]></category>
            <category><![CDATA[stencil]]></category>
            <category><![CDATA[ionic]]></category>
            <dc:creator><![CDATA[Cristian Olaru]]></dc:creator>
            <pubDate>Fri, 18 May 2018 11:46:09 GMT</pubDate>
            <atom:updated>2021-03-09T20:19:23.369Z</atom:updated>
            <content:encoded><![CDATA[<p>We present here how we created a <a href="https://www.webcomponents.org/">Web Component</a> using the <a href="https://stenciljs.com/">Stencil JS</a> tool. The component is a responsive panel displaying user cards. Each card has a user picture as background and shows some information about the user: online/offline status, social network provider, gender, name, country flag, number of views, media items, and likes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kSkjFQgPzP4-pePyVHVKEw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vupNCW_uG3SqARvMkSceRQ.png" /></figure><p>See the demo app live (<a href="https://webcomponentshub.firebaseapp.com/">https://webcomponentshub.firebaseapp.com/</a>). The source code is available on GitHub.</p><p><a href="https://github.com/WebNextNative/web-components/tree/master/src/components/users-cards">WebNextNative/web-components</a></p><p>The web component is responsive: if we resize the window size, the cards will be rendered to accommodate the space. The component accepts just one parameter, the number of columns (if no value is specified, then a default value is used based on the window size):</p><pre>&lt;users-cards&gt;&lt;/users-cards&gt;<br>&lt;users-cards columns=”4&quot; &gt;&lt;/users-cards&gt;</pre><p>Also, we store the data model for our component on the <a href="https://developer.mozilla.org/en-US/docs/Web/API/Window/localStorage">browser localStorage</a> as an array of JSON objects — we decoupled the model from the view. The component has unit tests for ensuring the right behavior.</p><h4>Web components and tools</h4><p>First, what are Web Components? Web Components are custom HTML tags that can be created by the developers and can be used and reused in Web pages (similar to the already defined HTML tags). They are supported natively by modern browsers. Also, some polyfills (helper JS scripts) for the browsers that are not supporting this technology natively: <a href="https://www.webcomponents.org/polyfills">https://www.webcomponents.org/polyfills</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DepFE6jMHex9EcAfNs0iSQ.png" /><figcaption>Web components browsers support</figcaption></figure><p>For creating these custom components, some specifications are defined at <a href="https://www.w3.org/">W3C</a>:<br>- <a href="https://w3c.github.io/webcomponents/spec/custom/">Custom Elements </a>— a way to describe the custom HTML tags<br>- <a href="https://w3c.github.io/webcomponents/spec/shadow/">Shadow DOM</a> — a way to apply the style to the components in isolation —</p><p>There are some tools for creating Web components. One of them is <a href="https://www.polymer-project.org/">Polymer</a> (a project sponsored by Google). Starting with Polymer version 3, the web components are packaged as ES6 Modules and can be installed using <a href="https://www.npmjs.com/">NPM</a> — this will increase the technology&#39;s adaption. Another tool is <a href="https://stenciljs.com/">Stencil JS</a>, developed by the <a href="https://www.youtube.com/watch?v=UfD-k7aHkQE">Ionic Team</a>. We use it for creating our web component. We started our component with the <a href="https://stenciljs.com/pwa">PWA toolkit</a> (<a href="https://stenciljs.com/pwa">https://stenciljs.com/pwa</a>) because we use the Ionic grid for arranging our cards.</p><h4>Creating the Web component</h4><p>We clone the PWA toolkit project locally. Then we created a new folder structure for our component:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VquQBGJmxpz_AsL6UpR78w.png" /></figure><p>Our component code is located in <strong>users-cards.tsx</strong> Typescript file.</p><pre><strong>import </strong>{Component, Listen, Prop, State} <strong>from </strong>&#39;@stencil/core&#39;;<br><br>@Component({<br>  tag: &#39;users-cards&#39;,<br>  styleUrl: &#39;users-cards.scss&#39;,<br>  shadow: <strong>true<br></strong>})<br><strong>export class </strong>UsersCards {<br><br>  @Prop() columns: <strong>string</strong>;<br>  @State() cardsPerRow: <strong>number</strong>;<br><br>  @Listen(&#39;window:resize&#39;)<br>  windowResize() {<br>    console.log(&#39;Params columns: &#39; + <strong>this</strong>.columns);<br>    <strong>if</strong>(<strong>this</strong>.columns) {<br>      <strong>this</strong>.cardsPerRow = +<strong>this</strong>.columns<br>    } <strong>else </strong>{<br>      <strong>let </strong>width = window.innerWidth<br>      console.log(width)<br>      <strong>if </strong>(width &lt;= 540) {<br>        <strong>this</strong>.cardsPerRow = 2;<br>      }<br>      <strong>if </strong>(width &gt; 540 &amp;&amp; width &lt;= 960) {<br>        <strong>this</strong>.cardsPerRow = 4;<br>      }<br>      <strong>if </strong>(width &gt; 960 &amp;&amp; width &lt;= 1140) {<br>        <strong>this</strong>.cardsPerRow = 6;<br>      }<br>      <strong>if </strong>(width &gt; 1140) {<br>        <strong>this</strong>.cardsPerRow = 10;<br>      }<br>    }<br>    console.log(&#39;Component is about to be rendered. Columns: &#39; + <strong>this</strong>.cardsPerRow);<br>  }<br><br>  <em>/**<br>   * Component Lifecycle Method<br>   */<br>  </em>componentWillLoad() {<br>    <strong>this</strong>.windowResize()<br>  }<br><br>  getCardsMatrix(): Array&lt;Array&lt;<strong>any</strong>&gt;&gt;  {<br>    <strong>let </strong>cards = JSON.parse(window.localStorage.getItem(&quot;users_cards&quot;))<br>    <strong>if</strong>(cards) {<br>      <strong>let </strong>rows = cards.reduce((acc, card, currentIndex) =&gt; {<br>        <strong>if </strong>(currentIndex % <strong>this</strong>.getCardsPerRow() == 0 &amp;&amp; currentIndex !== 0) {<br>          acc.push([]);<br>        }<br>        acc[acc.length - 1].push(card);<br>        <strong>return </strong>acc;<br>      }, [[]]);<br>      // console.log(JSON.stringify(rows, null, 2))<br>      <strong>return </strong>rows<br>    } <strong>else </strong>{<br>      <strong>return </strong>[]<br>    }<br>  }<br><br>  getCardsPerRow(): <strong>number </strong>{<br>    <strong>if</strong>(<strong>this</strong>.columns) {<br>      <strong>this</strong>.cardsPerRow = +<strong>this</strong>.columns<br>      <strong>return this</strong>.cardsPerRow;<br>    } <strong>else </strong>{<br>      <strong>return this</strong>.cardsPerRow;<br>    }<br>  }<br><br>  render() {<br>    <strong>return </strong>(<br>      &lt;ion-grid class=&quot;ion-cards-container&quot;&gt;<br>        {<strong>this</strong>.getCardsMatrix().map((row) =&gt;<br>          &lt;ion-row&gt;<br>            {row.map((card) =&gt;<br><br>              &lt;ion-col class=&quot;ion-card&quot; style={{ backgroundImage: &quot;url(https://medium.com/&quot;%20+%20card.avatarUrl%20+%20&quot;)&quot;}}&gt;<br>                &lt;div class=&quot;overlay&quot;&gt;&lt;/div&gt;<br>                &lt;div class=&quot;content-wrapper&quot;&gt;<br>                  &lt;h4&gt;{card.title}&lt;/h4&gt;<br>                  &lt;div&gt;<br>                    &lt;a&gt;<br>                      &lt;span class=&quot;number&quot;&gt;&lt;strong&gt;{card.views}&lt;/strong&gt;&lt;/span&gt;<br>                      &lt;ion-icon color=&quot;primary&quot; name=&quot;eye&quot;&gt;&lt;/ion-icon&gt;<br>                    &lt;/a&gt;<br>                    &lt;a&gt;<br>                      &lt;span class=&quot;number&quot;&gt;&lt;strong&gt;{card.streams}&lt;/strong&gt;&lt;/span&gt;<br>                      &lt;ion-icon color=&quot;primary&quot; name=&quot;videocam&quot;&gt;&lt;/ion-icon&gt;<br>                    &lt;/a&gt;<br>                    &lt;a&gt;<br>                      &lt;span class=&quot;number&quot;&gt;&lt;strong&gt;{card.likes}&lt;/strong&gt;&lt;/span&gt;<br>                      &lt;ion-icon color=&quot;primary&quot; name=&quot;flag&quot;&gt;&lt;/ion-icon&gt;<br>                    &lt;/a&gt;<br>                  &lt;/div&gt;<br>                &lt;/div&gt;<br>                &lt;div&gt;<br>                  &lt;div class=&quot;content-badge&quot;&gt;<br>                    { card.online == &#39;online&#39;<br>                      ? &lt;ion-badge color=&quot;secondary&quot; item-end&gt;{card.online}&lt;/ion-badge&gt;<br>                      : ( card.online == &#39;offline&#39;<br>                          ? &lt;ion-badge color=&quot;primary&quot; item-end&gt;{card.online}&lt;/ion-badge&gt;<br>                          : &lt;ion-badge color=&quot;twitter&quot; item-end&gt;{card.online}&lt;/ion-badge&gt;<br>                      )<br>                    }<br>                  &lt;/div&gt;<br>                  &lt;div class=&quot;provider-badge&quot;&gt;<br>                    { card.provider == &#39;facebook.com&#39;<br>                      ? &lt;a target=&quot;_blank&quot; href=&quot;https://www.facebook.com/{card.uid}&quot;&gt;<br>                        &lt;ion-badge color=&quot;facebook&quot; item-end class=&quot;facebook&quot;&gt;<br>                          &lt;ion-icon name=&quot;logo-facebook&quot;&gt;&lt;/ion-icon&gt;<br>                        &lt;/ion-badge&gt;<br>                      &lt;/a&gt;<br>                      : ( card.provider == &#39;google.com&#39;<br>                          ? &lt;a target=&quot;_blank&quot; href=&quot;https://plus.google.com/{card.uid}&quot;&gt;<br>                            &lt;ion-badge color=&quot;google&quot; item-end class=&quot;google&quot;&gt;<br>                              &lt;ion-icon name=&quot;logo-google&quot;&gt;&lt;/ion-icon&gt;<br>                            &lt;/ion-badge&gt;<br>                          &lt;/a&gt;<br>                          : &lt;a target=&quot;_blank&quot; href=&quot;https://twitter.com/intent/user?user_id={card.uid}&quot;&gt;<br>                            &lt;ion-badge color=&quot;twitter&quot; item-end class=&quot;twitter&quot;&gt;<br>                              &lt;ion-icon name=&quot;logo-twitter&quot;&gt;&lt;/ion-icon&gt;<br>                            &lt;/ion-badge&gt;<br>                          &lt;/a&gt;<br>                      )<br>                    }<br>                  &lt;/div&gt;<br>                  &lt;div class=&quot;gender-badge&quot;&gt;<br>                    { card.gender == &#39;female&#39;<br>                      ? &lt;ion-badge item-end class=&quot;female&quot;&gt;<br>                          &lt;ion-icon name=&quot;female&quot; &gt;&lt;/ion-icon&gt;<br>                        &lt;/ion-badge&gt;<br>                      : &lt;ion-badge item-end&gt;<br>                          &lt;ion-icon name=&quot;male&quot;&gt;&lt;/ion-icon&gt;<br>                        &lt;/ion-badge&gt;<br>                    }<br>                  &lt;/div&gt;<br>                  &lt;div class=&quot;locale-badge&quot;&gt;<br>                    { card.country<br>                      ? &lt;img src={&#39;/assets/img/flags_iso/24/&#39; + card.country + &#39;.png&#39;}/&gt;<br>                      : &lt;div/&gt;<br>                    }<br>                  &lt;/div&gt;<br>                &lt;/div&gt;<br>              &lt;/ion-col&gt;<br>            )}<br>          &lt;/ion-row&gt;<br>        )}<br>      &lt;/ion-grid&gt;<br>    );<br>  }<br>}</pre><p>We use the <a href="http://twitter.com/Component"><em>@Component</em></a> decorator for specifying the component name (<strong>tag</strong>) and style (<strong>styleUrl</strong>). We specify just one parameter for the component (<strong>columns</strong>) using the <a href="http://twitter.com/Prop"><em>@Prop</em></a> decorator. We marked one <a href="http://twitter.com/State"><em>@State</em></a> variable (<strong>cardsPerRow</strong>) — any change to this variable value will render the component again.</p><p>We have one <strong>render()</strong> method responsible for the component rendering — is a <strong>JSX</strong> template with a mixture of tags and scripting — Stencil is borrowing this technology from React. Here we reuse some Ionic components like <strong>&lt;ion-row&gt; &lt;ion-icon&gt; &lt;ion-icon&gt;</strong>. The JS code is wrapped in curly braces <strong>{}</strong>.</p><p>We implemented <strong>componentWillLoad()</strong> lifecycle method also for making the component responsive. We listen for <a href="http://twitter.com/Listen"><em>@Listen</em></a><em>(‘window:resize’)</em> on <strong>windowResize()</strong> method — every time we change the window size — the component will be rendered again. The method <strong>getCardsMatrix()</strong> is used for creating an array of arrays from the array of card data.</p><h4>The component data</h4><p>The data model is declared on <strong>users-cards-model.ts</strong> file and is an array of JSON objects having this structure:</p><pre>[{<br> “avatarUrl”: “https://firebasestorage.googleapis.com/v0/b/glamorous-chat.appspot.com/o/avatars%2FexcanpHrbkNqgLtGJ9XpWTMZOiD2.jpg?alt=media&amp;token=bff06f16-6969-4685-bfea-4fe732e3e19f&quot;,<br> “date”: “2018–05–15T22:18:21.441Z”,<br> “fullName”: “Catalina Ichim”,<br> “hasOverlay”: <strong>true</strong>,<br> “gender”: “female”,<br> “key”: “excanpHrbkNqgLtGJ9XpWTMZOiD2”,<br> “likes”: 4,<br> “online”: “offline”,<br> “provider”: “facebook.com”,<br> “score”: 5,<br> “sessionId”: “1_MX40NTk1MTY4Mn5-MTUyNjQ3MzY2Nzc1N35adGRTTXBmU1Fua1NQSWxsZVhJYUxxakh-fg”,<br> “streams”: 6,</pre><pre> “timestamp”: 1526422701441,<br> “title”: “Catalina Ichim”,<br> “uid”: “427321321062023”,<br> “views”: 2<br>},…]</pre><p>Before rendering the component, we store this data array on <strong>localStorage</strong>:</p><pre>window.localStorage.removeItem(“users_cards”)<br> window.localStorage.setItem(“users_cards”, JSON.stringify(users_cards))</pre><p>The component with this call uses the data:</p><pre>let cards = JSON.parse(window.localStorage.getItem(“users_cards”))</pre><h4>Testing the component</h4><p>The Unit tests for the component are in the users-cards.spec.ts file.</p><pre><strong>import </strong>{ flush, render } <strong>from </strong>&#39;@stencil/core/testing&#39;;<br><strong>import </strong>{ UsersCards } <strong>from </strong>&#39;./users-cards&#39;;<br><strong>import </strong>{users_cards} <strong>from </strong>&quot;./users-cards-model&quot;;<br><br><em>/**<br> *<br> * localStorage fake<br> */<br></em><strong>var </strong>localStorageMock = (() =&gt; {<br>  <strong>var </strong>store = {};<br><br>  <strong>return </strong>{<br>    getItem: <strong>function</strong>(key) {<br>      <strong>return </strong>store[key] || <strong>null</strong>;<br>    },<br>    setItem: <strong>function</strong>(key, value) {<br>      store[key] = value;<br>    },<br>    clear: <strong>function</strong>() {<br>      store = {};<br>    }<br>  };<br><br>})();<br><br>Object.defineProperty(window, &#39;localStorage&#39;, {<br>  value: localStorageMock<br>});<br><br><em>/**<br> * Unit tests<br> */<br><br></em>describe(&#39;users-cards&#39;, () =&gt; {<br>  it(&#39;should build&#39;, () =&gt; {<br>    expect(<strong>new </strong>UsersCards()).toBeTruthy();<br>  });<br><br>  describe(&#39;rendering&#39;, () =&gt; {<br>    <strong>let </strong>element;<br>    beforeEach(<strong>async </strong>() =&gt; {<br>      <br>      // init card values<br>      window.localStorage.clear()<br>      window.localStorage.setItem(&quot;users_cards&quot;, JSON.stringify(users_cards))<br><br>      // render tag<br>      element = <strong>await </strong>render({<br>        components: [UsersCards],<br>        html: &#39;&lt;users-cards&gt;&lt;/users-cards&gt;&#39;<br>      });<br>    });<br><br>    it(&#39;should work without parameters&#39;, <strong>async </strong>() =&gt; {<br><br>      <strong>let </strong>width = window.innerWidth<br>      console.log(&quot;Window width: &quot; + width)<br><br>      <strong>await </strong>flush(element);<br>      <strong>const </strong>list = element.querySelector(&#39;ion-row&#39;);<br>      expect(list.children.length).toEqual(6);<br>    });<br><br><br>    it(&#39;should work with parameters&#39;, <strong>async </strong>() =&gt; {<br><br>      <strong>let </strong>width = window.innerWidth<br>      console.log(&quot;Window width: &quot; + width)<br><br>      element.columns = &quot;4&quot;;<br>      <strong>await </strong>flush(element);<br>      <strong>const </strong>list = element.querySelector(&#39;ion-row&#39;);<br>      expect(list.children.length).toEqual(4);<br>    });<br><br>  });<br>});</pre><p>We use the <strong>Jasmine</strong> tool for testing — <strong>Behavior-Driven</strong> testing. We test if our component is working when we specify a <strong>column</strong> parameter or not. Because we use local storage for storing the data (this is available in the browser but not in our unit tests). We are forced to introduce some <a href="https://blog.pragmatists.com/test-doubles-fakes-mocks-and-stubs-1a7491dfa3da">fake objects</a> for emulating the <strong>localStorage</strong> with a local variable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IIpfAvUHqPqhEg8wvOkWAw.png" /></figure><h4>Styling the component</h4><p>The code for styling the component is in the <strong>users-cards.scss</strong> file. The style is applied to the component in isolation from the rest of the application style (<strong>shadow: true</strong> on <a href="http://twitter.com/Component"><em>@Component</em></a>).</p><pre>h4 {<br>  margin: 0;<br>  color: #fff;<br>  font-size: 1.3rem;<br>}<br>ion-grid,<br>ion-col {<br>  padding: 0;<br>}<br>.ion-card {<br>  background-repeat: no-repeat;<br>  background-size: cover;<br>}<br>ion-col {<br>  height: 180px;<br>  position: relative;<br>  border: 1px solid #000000; border-color: #ff0000 #0000ff;<br>}<br><br>.overlay,<br>.content-wrapper {<br>  position: absolute;<br>  top: 0;<br>  left: 0;<br>  height: 100%;<br>  width: 100%;<br>}<br>.overlay {<br>  background-color: rgba(0, 0, 0, .4);<br>}<br>.content-wrapper {<br>  text-align: center;<br>  display: flex;<br>  flex-direction: column;<br>  justify-content: flex-end;<br>}<br>.content-wrapper h4,<br>.content-wrapper p {<br>  margin: 0;<br>  color: #fff;<br>}<br>.content-wrapper p {<br>  color: #efefef;<br>}<br>.content-badge {<br>  justify-content: flex-start;<br>  margin-top: 3px;<br>  margin-left: 5px;<br>  color: #fff;<br>  position: absolute;<br>  top: 0;<br>  left: 0;<br>}<br>.provider-badge {<br>  justify-content: flex-start;<br>  margin-top: 3px;<br>  margin-right: 5px;<br>  color: #fff;<br>  position: absolute;<br>  top: 0;<br>  right: 0;<br>}<br>.gender-badge {<br>  justify-content: flex-start;<br>  margin-top: 27px;<br>  margin-right: 5px;<br>  color: #fff;<br>  position: absolute;<br>  top: 0;<br>  right: 0;<br>}<br>.locale-badge {<br>  justify-content: flex-start;<br>  margin-top: 50px;<br>  margin-right: 5px;<br>  color: #fff;<br>  position: absolute;<br>  top: 0;<br>  right: 0;<br>}<br>.number {<br>  color: #488aff;<br>  margin-left: 10px;<br>}<br><br>.twitter {<br>  background-color: #1dcaff<br>}<br>.facebook {<br>  background-color: #3b5998<br>}<br>.google {<br>  background-color: #d34836<br>}<br>.female {<br>  background-color: #d34836<br>}<br>.male {<br>  background-color: #3b5998<br>}</pre><p>Some styling aspects: <br>- we use an overlay for each card for making it darker and be able to show the username in white<br>- on each card, we use absolute positioning for the card elements<br>- we added the user picture as a background image to each card</p><h4>You can <a href="https://twitter.com/colaru">follow me on Twitter</a>, where I continue to document my next steps.</h4><h4>References</h4><p>Stencil tool: <a href="https://stenciljs.com/">https://stenciljs.com</a><br>Stencil docs: <a href="https://stenciljs.com/docs/introduction">https://stenciljs.com/docs/introduction</a><br>Stencil intro: <a href="https://www.youtube.com/watch?v=UfD-k7aHkQE">https://www.youtube.com/watch?v=UfD-k7aHkQE</a><br>Stencil video guides: <a href="https://www.youtube.com/watch?v=MqMYaT1GlWY">https://www.youtube.com/watch?v=MqMYaT1GlWY</a>, <a href="https://www.youtube.com/watch?v=g4jsOCUD4lA">https://www.youtube.com/watch?v=g4jsOCUD4lA</a>, <a href="https://www.youtube.com/watch?v=Yp_oiCWV_no">https://www.youtube.com/watch?v=Yp_oiCWV_no</a><br>Web Components intro: <a href="https://www.webcomponents.org/introduction">https://www.webcomponents.org/introduction</a><br>Web Components index: <a href="https://www.webcomponents.org/">https://www.webcomponents.org/</a><br>Polymer 3: <a href="https://www.polymer-project.org/">https://www.polymer-project.org/</a> <a href="https://www.youtube.com/watch?v=7CUO7PyD5zA">https://www.youtube.com/watch?v=7CUO7PyD5zA</a><br>W3C Custom Elements and Shadow DOM specs: <a href="https://w3c.github.io/webcomponents/spec/custom/">https://w3c.github.io/webcomponents/spec/custom/</a>,<a href="https://w3c.github.io/webcomponents/spec/shadow/">https://w3c.github.io/webcomponents/spec/shadow/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3753c20b1b12" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ionic-book/web-components-how-to-create-a-component-with-stencil-3753c20b1b12">Web Components — How we created a Web component with Stencil JS</a> was originally published in <a href="https://medium.com/ionic-book">Web Native</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How you can be 100% PWA]]></title>
            <link>https://medium.com/ionic-book/seo-step-by-step-8589f4ae7021?source=rss-91f1357cf9e5------2</link>
            <guid isPermaLink="false">https://medium.com/p/8589f4ae7021</guid>
            <category><![CDATA[pwa]]></category>
            <category><![CDATA[firehose-project]]></category>
            <category><![CDATA[google]]></category>
            <category><![CDATA[seo]]></category>
            <dc:creator><![CDATA[Cristian Olaru]]></dc:creator>
            <pubDate>Sat, 05 May 2018 08:03:02 GMT</pubDate>
            <atom:updated>2019-08-21T06:40:21.650Z</atom:updated>
            <content:encoded><![CDATA[<p>How you can be 100% PWA</p><p>In the previous article <a href="https://medium.com/ionic-book/seo-step-by-step-bc2ad2128b4e">SEO — with Google AMP, PWA, WorkBox and LightHouse</a> we presented how we can create an SEO optimized page with Google technologies more in a theoretical manner. Here we show some practical aspects that we find in optimizing the <a href="http://ionicbook.com/">ionicbook.com</a> site using <a href="https://developers.google.com/web/tools/lighthouse/">Light House for 100% PWA.</a> In this article, we will present more code, and a lot of screenshots.</p><p>First of all, we show you what we get in the end regarding performance using Google LightHouse tool:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tWCT1DTkpkrKXk6zoXYMsQ.png" /></figure><p>You can test this on your computer installing LightHouse as an extension to your Chrome browser and running the ‘Audits’ on ionicbook.com site (we recommend you to use a New incognito browser Window). You can find here <a href="https://developers.google.com/web/tools/lighthouse/#devtools">how to install and use LightHouse</a>.</p><p>For obtaining 100% PWA score we registered a service worker using <a href="https://developers.google.com/web/tools/workbox/">Google WorkBox</a>. You can see that we use it for pre-caching a set of pages, the CSS files, images, fonts. We also activated the offline Google Analytics. Here is the sw.js code:</p><pre>console.log(&#39;Hello from sw.js&#39;);<br><br>importScripts(&#39;https://storage.googleapis.com/workbox-cdn/releases/3.0.0/workbox-sw.js&#39;)<br><br><strong>if </strong>(workbox) {<br><br>    console.log(&#39;Yay! Workbox is loaded&#39;);<br><br>    workbox.setConfig({<br>        debug: <strong>false<br>    </strong>});<br><br><br>    // precaching<br>    workbox.precaching.precache([<br>        &#39;/&#39;,<br>        &#39;/404.html&#39;,<br>        &#39;/contact.html&#39;,<br>        &#39;/about.html&#39;,<br>        &#39;/img/ionic-4-book-cover.png&#39;,<br>        &#39;/img/ionic-4-book-cover.webp&#39;,<br>        &#39;/img/logos/logo_48.png&#39;,<br>        {<br>            url: &#39;/index.html&#39;,<br>            revision: &#39;as46&#39;,<br>        }<br>    ]);<br><br>    // cache start url<br>    // workbox.routing.registerNavigationRoute(&#39;/&#39;);<br><br>    // Cache JavaScript and CSS<br>    workbox.routing.registerRoute(<br>        <strong>new </strong>RegExp(&#39;.*\.js&#39;),<br>        workbox.strategies.networkFirst()<br>    );<br>    workbox.routing.registerRoute(<br>        // Cache CSS files<br>        /.*\.css/,<br>        // Use cache but update in the background ASAP<br>        workbox.strategies.staleWhileRevalidate({<br>            // Use a custom cache name<br>            cacheName: &#39;css-cache&#39;,<br>        })<br>    );<br><br><br>    // Cache Images<br>    workbox.routing.registerRoute(<br>        // Cache image files<br>        /.*\.(?:png|jpg|jpeg|svg|gif)/,<br>        // Use the cache if it&#39;s available<br>        workbox.strategies.cacheFirst({<br>            // Use a custom cache name<br>            cacheName: &#39;image-cache&#39;,<br>            plugins: [<br>                <strong>new </strong>workbox.expiration.Plugin({<br>                    // Cache only 20 images<br>                    maxEntries: 20,<br>                    // Cache for a maximum of a week<br>                    maxAgeSeconds: 7 * 24 * 60 * 60,<br>                })<br>            ],<br>        })<br>    );<br><br>    // Cache Google Fonts<br>    workbox.routing.registerRoute(<br>        <strong>new </strong>RegExp(&#39;^https://fonts.(?:googleapis|gstatic).com/(.*)&#39;),<br>        workbox.strategies.cacheFirst()<br>    );<br><br>    // Offline Google Analytics<br>    workbox.googleAnalytics.initialize();<br>}<br><strong>else </strong>{<br>    console.log(&#39;Boo! Workbox didnt load &#39;);<br>}</pre><p>We declared the service worker in our index.html page:</p><pre>&lt;amp-install-serviceworker<br>        src=&quot;sw.js&quot;<br>        layout=&quot;nodisplay&quot;&gt;<br>&lt;/amp-install-serviceworker&gt;</pre><p>We can see now our Service Worker data and the caches in Developer Tools/Application (we can clean the caches using Clean storage option — this is very useful because the service worker will serve from the cache the configured pages and we will not see the changes we made to the pages):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZKCsPANJarUKFJisy6TPCw.png" /><figcaption>Service worker is registered</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Rcnl-QLIEFFEc1eIPdXiQQ.png" /><figcaption>You can see the cached files in Cache Storage</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7CdGIgOmQVBISXWvmfgwYQ.png" /><figcaption>You can clear the cache storage</figcaption></figure><p>Also we created a manifest for our app:</p><pre>{<br>  &quot;name&quot;: &quot;Ionic Book&quot;,<br>  &quot;short_name&quot;: &quot;Ionic 4 Book&quot;,<br>  &quot;start_url&quot;: &quot;/index.html&quot;,<br>  &quot;display&quot;: &quot;standalone&quot;,<br>  &quot;icons&quot;: [<br>    {<br>      &quot;src&quot;: &quot;img/logos/logo_48.png&quot;,<br>      &quot;type&quot;: &quot;image/png&quot;,<br>      &quot;sizes&quot;: &quot;48x48&quot;<br>    },<br>    {<br>      &quot;src&quot;: &quot;img/logos/logo_96.png&quot;,<br>      &quot;type&quot;: &quot;image/png&quot;,<br>      &quot;sizes&quot;: &quot;96x96&quot;<br>    },<br>    {<br>      &quot;src&quot;: &quot;img/logos/logo_192.png&quot;,<br>      &quot;type&quot;: &quot;image/png&quot;,<br>      &quot;sizes&quot;: &quot;192x192&quot;<br>    },<br>    {<br>      &quot;src&quot;: &quot;img/logos/logo_512.png&quot;,<br>      &quot;type&quot;: &quot;image/png&quot;,<br>      &quot;sizes&quot;: &quot;512x512&quot;<br>    }<br>  ],<br>  &quot;background_color&quot;: &quot;#298fff&quot;,<br>  &quot;theme_color&quot;: &quot;#298fff&quot;,<br>  &quot;prefer_related_applications&quot;: <strong>false</strong>,<br>  &quot;related_applications&quot;: [<br>    {<br>      &quot;platform&quot;: &quot;play&quot;,<br>      &quot;id&quot;: &quot;com.ionicbook.mobile&quot;<br>    }<br>  ]<br>}</pre><p>We have to include the manifest in our index.html page:</p><pre>&lt;link rel=&quot;manifest&quot; href=&quot;/manifest.json&quot;&gt;</pre><p>We can see now our data in Chrome Developer Tools/Application/Manifest:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NvTeM_z15ekUa4KdlTd1Sg.png" /><figcaption>All manifest data is reflected in Light House</figcaption></figure><p>The most important aspect is that your page will be saved (you will be asked to do this) as an application and will appear in the list of the installed apps on the device:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nykiAtapKlVxI0PB0QEpYA.png" /></figure><p>References:</p><p>Status of service workers support: <a href="https://www.infoq.com/news/2018/05/service-workers-supported-across">https://www.infoq.com/news/2018/05/service-workers-supported-across</a></p><p>Google PWA: <a href="https://developers.google.com/web/progressive-web-apps/">https://developers.google.com/web/progressive-web-apps/</a></p><p>PWA on Windows 10: <a href="https://developer.microsoft.com/en-us/windows/pwa">https://developer.microsoft.com/en-us/windows/pwa</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8589f4ae7021" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ionic-book/seo-step-by-step-8589f4ae7021">How you can be 100% PWA</a> was originally published in <a href="https://medium.com/ionic-book">Web Native</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ionic 4 Book]]></title>
            <link>https://medium.com/series/ionic-4-book-8527bb59aca3?source=rss-91f1357cf9e5------2</link>
            <guid isPermaLink="false">https://medium.com/p/8527bb59aca3</guid>
            <dc:creator><![CDATA[Cristian Olaru]]></dc:creator>
            <pubDate>Thu, 03 May 2018 07:17:45 GMT</pubDate>
            <atom:updated>2018-05-03T07:28:15.996Z</atom:updated>
            <content:encoded><![CDATA[<p>You can buy the <a href="https://leanpub.com/ionic4">Ionic 4 book</a>.</p><p>You can visit the <a href="https://ionicbook.com/">presentation sit</a>e.</p><p>You can <a href="https://medium.com/ionic-book">read our blog</a>.</p><p><strong>In this Ionic 4 book, you will learn everything you need to know for developing hybrid mobile applications for Android, iOs and Windows Phone devices and for publishing them in the corresponding application stores: Google Play Store, Apple App Store, Microsoft Store. We can name this book ‘From 0 to the app store’ but we preferred to use the ‘Step by step’ subtitle for showing the practical nature of this book.</strong></p><p><strong>And because the new Ionic 4 is not just about mobile, you will learn how to host our apps as PWA web applications on AWS S3 or Google Firebase and be accessible from all the modern browsers like Google Chrome, Apple Safari, Windows Edge or Firefox. Or how to package our applications as desktop applications using Electron for operating systems like Windows, MacOs or Linux.</strong></p><p><strong>You will also learn how to use a server-less backend for our Ionic applications because in these days is better to use multiple cloud (micro)services and not to manage a massive application server for the backend of our apps. You will learn how can achieve this using Google Firebase or AWS ecosystem (Lambda, API Gateway, S3). You will learn how to use external services like Google and Firebase Analytics for our KPI metrics, OneSignal for push notifications, Login with social networks (like Facebook, Google Plus, Twitter), WebRTC, etc.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8527bb59aca3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ionic 4 — The Vision]]></title>
            <link>https://medium.com/ionic-book/ionic-4-the-vision-3afd8b21067e?source=rss-91f1357cf9e5------2</link>
            <guid isPermaLink="false">https://medium.com/p/3afd8b21067e</guid>
            <category><![CDATA[vuejs]]></category>
            <category><![CDATA[ionic]]></category>
            <category><![CDATA[stenciljs]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[electron]]></category>
            <dc:creator><![CDATA[Cristian Olaru]]></dc:creator>
            <pubDate>Mon, 30 Apr 2018 10:01:37 GMT</pubDate>
            <atom:updated>2018-08-08T06:55:12.464Z</atom:updated>
            <content:encoded><![CDATA[<p>The Ionic 4 vision is mighty. So great that I can’t imagine something similar on the market. If Ionic 3 was a way to create mobile applications, Ionic 4 is for creating all types of applications: mobile, web, desktop.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iyM6lpwc4JknJyDyFYYedA.png" /></figure><h4>Write once run everywhere</h4><p>One code for all platforms with <a href="https://capacitor.ionicframework.com/">Capacitator</a>, <a href="https://cordova.apache.org/">Apache Cordova</a>, <a href="https://electronjs.org/">Github Electron JS</a>. So we have to write one Web application and we can host it as a static Web app (PWA), package it and publish it to the mobile app stores, or package it as a desktop application and let the users download and install it.</p><p>- Mobile<br> — Android<br> — iOs<br> — Windows<br>- Web<br> — browser<br> — Google Chrome<br> — Apple Safari<br> — Microsoft Edge<br> — Firefox<br> — others<br> — Web PWA<br>- Desktop<br> — Mac<br> — Linux<br> — Windows<br> — <a href="https://developers.google.com/web/updates/2018/05/nic67#desktop-pwas">Desktop PWA</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JrTD8CjOgf4hca48R0GyiQ.png" /></figure><h4>Framework agnostic</h4><p><a href="https://www.webcomponents.org/">Web components</a> and <a href="https://stenciljs.com/">Stencil</a><br> — Angular<br> — React JS<br> — Vue JS<br> — none or the framework of the future</p><p><strong>Old pillars still available<br></strong>- Cordova<br>- Angular</p><h4>Other solutions on the market</h4><p><strong>Native Script<br></strong>Site: <a href="https://www.nativescript.org/">https://www.nativescript.org/</a><br>Resources: <a href="https://market.nativescript.org/">https://market.nativescript.org/</a><br><strong>React Native (Facebook)<br></strong>Site: <a href="https://facebook.github.io/react-native/">https://facebook.github.io/react-native/</a><br>Resources: <a href="http://www.awesome-react-native.com/">http://www.awesome-react-native.com/</a><br><strong>Flutter (Google)</strong><br>Site: <a href="https://flutter.io/">https://flutter.io/</a><br>Resources: <a href="https://github.com/Solido/awesome-flutter">https://github.com/Solido/awesome-flutter</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3afd8b21067e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ionic-book/ionic-4-the-vision-3afd8b21067e">Ionic 4 — The Vision</a> was originally published in <a href="https://medium.com/ionic-book">Web Native</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Awesome Ionic 4 — List of Ionic 4 resources]]></title>
            <link>https://medium.com/ionic-book/list-of-ionic-4-resources-509067dd1a43?source=rss-91f1357cf9e5------2</link>
            <guid isPermaLink="false">https://medium.com/p/509067dd1a43</guid>
            <category><![CDATA[vuejs]]></category>
            <category><![CDATA[stenciljs]]></category>
            <category><![CDATA[ionic]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[angular]]></category>
            <dc:creator><![CDATA[Cristian Olaru]]></dc:creator>
            <pubDate>Mon, 30 Apr 2018 06:25:23 GMT</pubDate>
            <atom:updated>2018-08-08T18:41:23.894Z</atom:updated>
            <content:encoded><![CDATA[<p><strong><em>This is the list of resources for </em></strong><a href="https://blog.ionicframework.com/announcing-ionic-4-beta/"><strong><em>Ionic 4 Beta (</em></strong>4.0.2<strong><em>)</em></strong></a><strong><em> released on 8 August 2018. There is no GA release yet, and some links are still not final.</em></strong></p><h3>ionic on Twitter</h3><p>🔥 Introducing Ionic 4 Beta! 🔥 📈 Performance &amp;amp; build time improvements 🅰 Angular CLI &amp;amp; Router 🌍 Modern Web APIs (Custom Elements, Shadow DOM) 🎨 Powerful theming + CSS Variables 📃 Brand new Documentation 🤙 Help us test the best darn version yet: https://t.co/WI2ByWuysI</p><h3>ionic on Twitter</h3><p>Ionic v4 beta 2 is out! 🚀 🔘 Includes many bug fixes in preparation for the RC: https://t.co/wOcKNX8prj 🔘 Also, @GitHub&#39;s project board is ✨ AWESOME ✨ https://t.co/yOUsJtjhVj</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*njf-6YnIWCoabB0aPO5ZGA.jpeg" /></figure><p>We present here the most important Ionic 4 resources: technologies, articles, videos. This page is a work in progress, and new links will be added in time.</p><p>First a preview of the Ionic 4 stack:</p><h3>Max Lynch on Twitter</h3><p>Trying diagrams to explain the moving parts of the upcoming Ionic app stack. Think of your app as a Virtual Machine image, with Capacitor (or Cordova) as the Hypervisor letting your app run seamlessly on iOS, Android, Electron, and as a PWA on the web. @Ionicframework</p><p>Here is a list of Ionic 4 resources:</p><h3><strong>Technologies</strong></h3><h4>Ionic 4</h4><p>The blog post announcing Ionic 4 Beta: <a href="https://blog.ionicframework.com/announcing-ionic-4-beta/">https://blog.ionicframework.com/announcing-ionic-4-beta</a>/<br>Ionic 4 Beta docs: <a href="https://beta.ionicframework.com/docs/">https://beta.ionicframework.com/docs/</a><br>Ionic 4 Beta Web Components — <a href="https://beta.ionicframework.com/docs/components">https://beta.ionicframework.com/docs/components</a>\<br>Ionic Native 5.0 — <a href="https://beta.ionicframework.com/docs/native">https://beta.ionicframework.com/docs/native</a><br>Ionic 4 Beta CLI — <a href="https://beta.ionicframework.com/docs/cli/overview">https://beta.ionicframework.com/docs/cli/overview</a><br>IonIcons 4.0 — <a href="https://ionicons.com/">https://ionicons.com/</a></p><h4>Awesome resources related to Ionic 4</h4><p>Awesome Angular: <a href="https://github.com/gdi2290/awesome-angular">https://github.com/gdi2290/awesome-angular</a><br>Awesome iOs: <a href="https://github.com/vsouza/awesome-ios">https://github.com/vsouza/awesome-ios</a><br>Awesome Android: <a href="https://github.com/JStumpp/awesome-android">https://github.com/JStumpp/awesome-android</a><br>Awesome Stencil: <a href="https://github.com/mappmechanic/awesome-stenciljs">https://github.com/mappmechanic/awesome-stenciljs</a><br>Awesome Firebase: <a href="https://github.com/afonsopacifer/awesome-firebase">https://github.com/afonsopacifer/awesome-firebase</a><br>Awesome TypeScript: <a href="https://github.com/dzharii/awesome-typescript">https://github.com/dzharii/awesome-typescript</a></p><p>Awesome React Native (see the enemy): <a href="https://github.com/jondot/awesome-react-native">https://github.com/jondot/awesome-react-native</a><br>Awesome Native Script (see the enemy): <a href="https://github.com/DeviantJS/awesome-nativescript">https://github.com/DeviantJS/awesome-nativescript</a></p><h4>Capacitator &amp; Cordova</h4><p>Capacitator Site — <a href="https://capacitor.ionicframework.com/">https://capacitor.ionicframework.com/</a><br>Cordova — <a href="https://cordova.apache.org/">https://cordova.apache.org/</a><br>Cordova plugins — <a href="https://cordova.apache.org/plugins/">https://cordova.apache.org/plugins/</a><br>Ionic Native — <a href="https://beta.ionicframework.com/docs/native">https://beta.ionicframework.com/docs/native</a></p><h4>Stencil &amp; Web Components</h4><p>Stencil Site— <a href="https://stenciljs.com/">https://stenciljs.com/</a><br>Awesome Stencil — <a href="https://github.com/mappmechanic/awesome-stenciljs">https://github.com/mappmechanic/awesome-stencilj</a>s</p><p>Web components — <a href="https://www.webcomponents.org/">https://www.webcomponents.org/</a><br>Polymer — <a href="https://www.polymer-project.org/">https://www.polymer-project.org/</a><br>Angular Elements — <a href="https://angular.io/guide/elements">https://angular.io/guide/elements</a></p><h4>Others Ionic 4 resources</h4><p>Ionic PWA toolkit — <a href="https://github.com/ionic-team/ionic-pwa-toolkit">https://github.com/ionic-team/ionic-pwa-toolkit</a><br>Electron — <a href="https://electronjs.org/">https://electronjs.org/</a><br>Angular — <a href="https://angular.io/">https://angular.io/</a> (google)<br>TypeScript — <a href="https://www.typescriptlang.org/">https://www.typescriptlang.org/</a><br>Ionic Themer — <a href="https://ionthemer.com/">https://ionthemer.com/</a><br>Ionic Marketplace — <a href="https://market.ionicframework.com/">https://market.ionicframework.com/</a></p><h4>PWA &amp; Related technologies</h4><p>Web PWA — <a href="https://developers.google.com/web/progressive-web-apps/">https://developers.google.com/web/progressive-web-apps/</a><br>Desktop PWA — <a href="https://developers.google.com/web/updates/2018/05/nic67#desktop-pwas">https://developers.google.com/web/updates/2018/05/nic67#desktop-pwas</a><br>WorkBox — <a href="https://developers.google.com/web/tools/workbox/">https://developers.google.com/web/tools/workbox/</a><br>LightHouse — <a href="https://developers.google.com/web/tools/lighthouse/">https://developers.google.com/web/tools/lighthouse/</a><br>Google AMP — <a href="https://www.ampproject.org/">https://www.ampproject.org/</a></p><h4>Serverless backends</h4><p>Amazon AWS — <a href="https://aws.amazon.com/">https://aws.amazon.com/</a><br>One Signal — <a href="https://onesignal.com/">https://onesignal.com/</a><br>Google Firebase — <a href="https://firebase.google.com/">https://firebase.google.com/</a></p><h4>LAF</h4><p>Twitter Bootstrap — <a href="https://getbootstrap.com/">https://getbootstrap.com/</a><br>Material Design — <a href="https://material.io/">https://material.io/</a><br>iOs Human Interface— <a href="https://developer.apple.com/design/human-interface-guidelines/">https://developer.apple.com/design/human-interface-guidelines/</a></p><h3>Articles</h3><ul><li><a href="https://blog.ionicframework.com/ionic-2017-18-roadmap/">Ionic: 2017-18 Roadmap</a></li><li><a href="https://blog.ionicframework.com/announcing-capacitor-1-0-0-alpha/">Announcing Capacitor 1.0.0 Alpha</a></li><li><a href="https://www.joshmorony.com/what-to-expect-when-ionic-4-is-released/">What to Expect When Ionic 4 Is Released</a></li><li><a href="https://medium.com/@cwoolum/upgrading-to-ionic-4-e2cdff9fc76d">Upgrading to Ionic 4</a></li><li><a href="https://www.joshmorony.com/using-ionic-with-any-framework-or-none-at-all/">Using Ionic with Any Framework (or None at All)</a></li><li><a href="https://alligator.io/vuejs/vue-ionic/">Using Ionic 4 Components in Your Vue.js Apps</a></li></ul><h3>Videos</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FUfD-k7aHkQE%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DUfD-k7aHkQE&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FUfD-k7aHkQE%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/8e1a9782d8098c3257e4aa15020ad49e/href">https://medium.com/media/8e1a9782d8098c3257e4aa15020ad49e/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FimaTBx4jbwY%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DimaTBx4jbwY&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FimaTBx4jbwY%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/c59cb2be6749c40e769e173fdac27411/href">https://medium.com/media/c59cb2be6749c40e769e173fdac27411/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fx2jRs7Qqai8%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dx2jRs7Qqai8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fx2jRs7Qqai8%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/56f95edba96784a9a460d0829909cd3e/href">https://medium.com/media/56f95edba96784a9a460d0829909cd3e/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F0ki8tXYocjI%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D0ki8tXYocjI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F0ki8tXYocjI%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/40d0de0c9335f16ecd9fdf2c3be64423/href">https://medium.com/media/40d0de0c9335f16ecd9fdf2c3be64423/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F34fDUKaJBtw%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D34fDUKaJBtw&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F34fDUKaJBtw%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/db8e68c6bb63ff8d21328b035431f26a/href">https://medium.com/media/db8e68c6bb63ff8d21328b035431f26a/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Frb8smP_xTTY%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Drb8smP_xTTY&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Frb8smP_xTTY%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/a99397e46fb426004e754b66e798111f/href">https://medium.com/media/a99397e46fb426004e754b66e798111f/href</a></iframe><pre>https://www.recallact.com/presentation/stenciljs-and-universal-components</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=509067dd1a43" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ionic-book/list-of-ionic-4-resources-509067dd1a43">Awesome Ionic 4 — List of Ionic 4 resources</a> was originally published in <a href="https://medium.com/ionic-book">Web Native</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SEO with Google tools]]></title>
            <link>https://medium.com/ionic-book/seo-step-by-step-bc2ad2128b4e?source=rss-91f1357cf9e5------2</link>
            <guid isPermaLink="false">https://medium.com/p/bc2ad2128b4e</guid>
            <category><![CDATA[google-search-console]]></category>
            <category><![CDATA[seo]]></category>
            <category><![CDATA[amp]]></category>
            <category><![CDATA[mobile-first]]></category>
            <dc:creator><![CDATA[Cristian Olaru]]></dc:creator>
            <pubDate>Sun, 29 Apr 2018 10:49:18 GMT</pubDate>
            <atom:updated>2021-03-09T20:13:22.388Z</atom:updated>
            <content:encoded><![CDATA[<h3>With Google AMP, PWA, WorkBox, and LightHouse</h3><p><em>We are trying to describe here all the simple steps needed for having an SEO (SEO = </em><a href="https://neilpatel.com/what-is-seo/"><em>Search Engine Optimization</em></a><em>) optimized static site. We describe here just the optimization needed for the Google Search engine (there are other search engines like Microsoft Bing). We assume you know how Google search works otherwise you need to read this Google page: </em><a href="https://www.google.com/search/howsearchworks/"><em>https://www.google.com/search/howsearchworks</em></a><em>. We use general Google tools for SEO optimization — please see the references list at the end.</em></p><p>Good article about Web optimization: <a href="https://medium.com/@fox/talk-the-state-of-the-web-3e12f8e413b3">https://medium.com/@fox/talk-the-state-of-the-web-3e12f8e413b3</a></p><p>We will show the steps on a real static site (no server-side backend, just landing pages) dedicated to a book named ionicbook.com. We will record here all the steps needed to make this site SEO-friendly. Let’s begin:</p><p><strong>Site domain and hosting</strong></p><p>First, we need a domain for the site. We will buy it! Our website is dedicated to an Ionic Framework book, so the name we prefer is <a href="http://ionibook.com/">ionicbook.com</a> because this domain is free. But it seems that the name of the site is not so important for SEO these days — maybe it was in the past. The more important is the content of the website that should express the scope of the site very precisely. So if you have to choose a domain — you better use a short name, easy to be remembered by your visitors — not necessarily related to the SEO keywords (or slowly related).</p><p>Be online as soon as possible. Because some time will pass till your site will be indexed by Google. So is good to be online as quickly as possible. Choose a hosting that can offer HTTPS to your application (Google is sensitive to this). You can use <a href="https://aws.amazon.com/cloudfront/">AWS CloudFront</a> + AWS S3, Google <a href="https://firebase.google.com/products/hosting/">Firebase Hosting</a>, or <a href="https://www.cloudflare.com/">Cloudflare</a> for HTTPS support and other facilities like resources caching, gzip-ing, DOS attacks protection, etc. Your hosting has to be fast and secure.</p><p><strong>Good content quality</strong></p><p>Then, we have to create the content for the site. These days is more important to have good content for good SEO results. You don’t need to do much work to optimize the site content for the Google search algorithm — we have to write good content like the search engine are not existing because the search algorithms are scoring well this type of material. See the official <a href="https://static.googleusercontent.com/media/www.google.com/en//insidesearch/howsearchworks/assets/searchqualityevaluatorguidelines.pdf">Google Search Quality Rating Guidelines</a>.</p><p>We will respect just a few rules. We will identify the main SEO keywords for our site but we not repeat them everywhere on the pages. Not too many times for avoiding “Keyword Stuffed pages”.<br>Instead, we will express the scope of the site using similar words in all these places:</p><ul><li>one call to action button</li><li>the main content (plain text) that is describing the scope of the site</li><li>a single page UVP = Unique Value Proposition in just one ‘H1’ tag per page</li><li>page title</li><li>meta description and meta keywords (it seems that meta keywords are losing their importance in the last time, but we will keep them)</li><li>descriptive page URL</li><li>ALT texts for images</li></ul><p>Other rules:<br>- the site has multiple landing pages but one clear home page<br>- we use canonical tags<br>- About and Contact pages for website information<br>- no copied content from other sites<br>- use specific lang for locale</p><p><strong>Improve Speed</strong></p><p>We will start to build the site using a landing page template and popular CSS framework for a good look and feel. While there a lot of landing page templates on the market (see <a href="https://themeforest.net/category/site-templates">Theme Forest</a> for example) and a lot of beautiful CSS frameworks like Twitter Bootstrap and Google Material Design we will use <a href="https://www.ampproject.org/">Google AMP</a> for the only reason — speed. Speed is also essential for SEO and application users, and AMP is the winner in this aspect.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h-VIUtb47SGKXyoqsPzM5A.png" /><figcaption>AMP site</figcaption></figure><p>AMP is using Web components technology and will let us quickly create a speedy website. It has a set of already done templates named AMPStart <a href="https://www.ampstart.com/">https://www.ampstart.com</a> and, we will use it as the starter for our site. Also, it is based on the Basscss framework <a href="http://basscss.com/">http://basscss.com/</a>, and we will have primary CSS support for grids, align, typography, layout, position, hide.</p><p><strong>Page audits — continuously</strong></p><p>We use the Google <a href="https://developers.google.com/web/tools/lighthouse/">Light House</a> tool in our site development process for auditing our pages (as a Google Chrome plugin integrated into the browser <a href="https://developers.google.com/web/tools/chrome-devtools/">DevTools</a>). This tool is essential in ensuring all aspects that are conducting to an optimized page: Performance, PWA, Accessibility, Best practices, SEO.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/784/1*b7kiSylyWZNbvUwphSbqlg.png" /><figcaption>Lighthouse tool</figcaption></figure><p>When our site is online, we have to check all the time the state of our SEO in Google Search Console, Google Analytics, or making search queries on google.com.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FctLONexk3MEW2w7849zVQ.png" /></figure><p><strong>Be mobile-first</strong></p><p>We have to be sure our site is responsive, and the mobile users have a good user experience (UX). This because we live in a time when the Google searches from mobile devices are higher than the searches from desktop devices. Any modern CSS framework is responsive to the device resolution so that this scope can be easily achieved our days. But we have to test our website on Google DEV Tools and on real devices to verify the UX. <a href="https://search.google.com/test/mobile-friendly">Here</a> you can test if your app is mobile-friendly.</p><p><a href="https://developers.google.com/web/progressive-web-apps/">PWA</a> is another aspect that we have to consider for our mobile users. We know that if our site can be accessed from a mobile device, that device can have a weak connection and even sometimes can become offline. In this case, we need to cache the site content and ensure the user has a pleasant experience. PWA is helping in this. And even more, we can let the user save the website on the device and see the web app as a native app — with this we encourage user retention. We use <a href="https://developers.google.com/web/tools/workbox/">Google WorkBox</a> for PWA.</p><p><strong>Register in Google Search Console</strong></p><p>We have to register our page in <a href="https://www.google.com/webmasters/tools/home">Google Search Console</a>. This tool is essential for letting Google know that a new page is on the Web — the Google crawler will come to index our page — we also can ask this manually. Also, you will receive emails from Google with suggestions for improving our site search performance, or we will be informed about our site problems.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xtMiVXbc5ZyGReQ24VqkKw.png" /><figcaption>Google Search Console Chart</figcaption></figure><p>We have to create a sitemap and upload it to the console — Google will know in this way what pages should be indexed. On the console, we can see the search analytics: impressions, clicks, CTR, page positions in SERP, top search queries, etc. We can see also the links to our site — internals and externals. The Google Search Console is the perfect place to see how our website is performing relating to the search.</p><p>We will also use other Google tools. We will add Google <a href="https://www.google.com/analytics/">Analytics</a> to our site to see what our visitors are doing. And we will use some ads from Google <a href="https://adwords.google.com/home/">AdWords</a> to get some test users on our website to look at their behaviors.</p><p><strong>Let’s recapitulate</strong></p><p>The site domain name is not important<br>Content is essential — write for the users, not for the search algorithm<br>Speed is critical — you have to check your site with HouseLight<br>Be mobile friendly and use HTTPS<br>Register your site with Google Search and follow their advice<br>Continuous SEO checks with tools: Google Search Console, LightHouse, Seo Analyzer</p><blockquote><strong>You can </strong><a href="https://twitter.com/colaru"><strong>follow me on Twitter</strong></a><strong> where I continue to document my next steps.</strong></blockquote><p><strong>Resources</strong></p><p>How Google search works — <a href="https://www.google.com/search/howsearchworks">https://www.google.com/search/howsearchworks</a><br>Google Search Quality Rating Guidelines -<br> <a href="https://static.googleusercontent.com/media/www.google.com/en//insidesearch/howsearchworks/assets/searchqualityevaluatorguidelines.pdf">https://static.googleusercontent.com/media/www.google.com/en//insidesearch/howsearchworks/assets/searchqualityevaluatorguidelines.pdf</a><br>SEO guy Neil Patel — <a href="https://neilpatel.com/what-is-seo/">https://neilpatel.com/what-is-seo/</a></p><p>Google Search Console — <a href="https://www.google.com/webmasters/tools/home">https://www.google.com/webmasters/tools/home</a><br>Google AMP — <a href="https://www.ampstart.com/">https://www.ampstart.com/</a><br>Google Analytics — <a href="https://www.google.com/analytics/">https://www.google.com/analytics/</a><br>Google AdWords — <a href="https://adwords.google.com/home/">https://adwords.google.com/home/</a><br>Google Lighthouse — <a href="https://developers.google.com/web/tools/lighthouse/">https://developers.google.com/web/tools/lighthouse/</a><br>Google Chrome DevTools -<br> <a href="https://developers.google.com/web/tools/chrome-devtools/">https://developers.google.com/web/tools/chrome-devtools/</a><br>Google WorkBox — <a href="https://developers.google.com/web/tools/workbox/">https://developers.google.com/web/tools/workbox/</a><br>Google PWA — <a href="https://developers.google.com/web/progressive-web-apps/">https://developers.google.com/web/progressive-web-apps/</a></p><p>Neil Patel Seo analyzer — <a href="https://neilpatel.com/seo-analyzer/">https://neilpatel.com/seo-analyzer/</a><br>Google mobile-friendly — <a href="https://search.google.com/test/mobile-friendly">https://search.google.com/test/mobile-friendly</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bc2ad2128b4e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ionic-book/seo-step-by-step-bc2ad2128b4e">SEO with Google tools</a> was originally published in <a href="https://medium.com/ionic-book">Web Native</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mobile — devices, operating systems and stores]]></title>
            <link>https://medium.com/ionic-book/mobile-devices-and-mobile-operating-systems-4cc9bcb1e17a?source=rss-91f1357cf9e5------2</link>
            <guid isPermaLink="false">https://medium.com/p/4cc9bcb1e17a</guid>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[app-store]]></category>
            <category><![CDATA[windows-phone]]></category>
            <category><![CDATA[google-play-store]]></category>
            <category><![CDATA[android]]></category>
            <dc:creator><![CDATA[Cristian Olaru]]></dc:creator>
            <pubDate>Fri, 27 Apr 2018 13:41:50 GMT</pubDate>
            <atom:updated>2018-05-03T07:07:12.490Z</atom:updated>
            <content:encoded><![CDATA[<p>There are a big number of <strong>smartphones</strong> and <strong>tablets</strong> on the market, each having a given operating system and it is produced by a given manufacturer. We live in the years when the number of mobile phones overcomes the number of desktop and laptop computers, and the difference is still growing (Google is reporting that there are more searches from mobile now than from desktops).</p><p>There are some stores today where we can publish our mobile application based on its operating system. There are <a href="http://www.idc.com/promo/smartphone-market-share/os">some signs</a> that the number of devices Android is the winner in the market (~70%), followed by iOS (~20%). Windows Phone has just a few percents but they choose to invest in mobile in the last time and our application can also be available to other Windows 10 devices like PC, tablet, Xbox due to <a href="https://docs.microsoft.com/en-us/windows/uwp/get-started/whats-a-uwp">UWP</a> (Windows 10 is around 25% from desktop OS market). Here is the list of major mobile operating systems on the market:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s-isJguj6-mSmNPVBbJP5w.png" /></figure><h4>Android OS</h4><p>Google is the owner of <a href="https://www.android.com/">Android OS</a>, and the devices are manufactured by many others like Samsung, Motorola, etc. There is a reference device <a href="https://madeby.google.com/phone">Google Pixel</a> series manufactured by Google. Till now it was Nexus, but the manufacturer was not Google. The programming language is Java (Android is derived from Java), and the development tool is Android Studio (based on IntelliJ Idea now, in the past was Eclipse) which can run on Linux, Windows or Mac operation systems.</p><h4>iOs OS</h4><p>Apple is the owner of the <a href="http://www.apple.com/ios">iOs operating system</a> and is also the manufacturer of the <a href="http://www.apple.com/iphone">iPhones</a> and <a href="http://www.apple.com/ipad">iPads</a>. The programming language in <a href="https://developer.apple.com/library/content/documentation/Cocoa/Conceptual/ProgrammingWithObjectiveC/Introduction/Introduction.html">Objective C</a> with the addition of a more scripting language named <a href="https://developer.apple.com/swift/">Swift</a>. The development tool is named <a href="https://developer.apple.com/xcode">XCode</a>, and we need a Mac OS system to develop our application.</p><h4>Windows Phone OS</h4><p>Microsoft is the owner of <a href="https://www.microsoft.com/en/mobile/windows10">Windows Phone</a> operating system and is manufacturing itself some physical devices — based on <a href="https://www.microsoft.com/en/mobile/phones/lumia">acquired Nokia</a> company. Starting with version 10, the Windows and Windows Phone are sharing the same store and is possible to publish a mobile app and will be available on mobile and desktop at the same time due to <a href="https://docs.microsoft.com/en-us/windows/uwp/get-started/universal-application-platform-guide">Universal Windows Platform — UWP</a>. We can program in C# or other <strong>.Net</strong> language. The development tool is <a href="https://www.visualstudio.com/">Microsoft Visio Studio</a> available on Windows OS.</p><p>It is hard to develop applications for all the stores because we have to know a multitude of languages Android(Java) for Java, Objective-C or Swift for iOs, C# or Visual Basic for Windows. A solution for this (write once publish everywhere) is to create hybrid applications using tools like <a href="https://ionicframework.com/">Ionic</a>.</p><h3>Mobile App stores</h3><p>Publishing to the app store is simple in the case of Google Play store because there are no so many reviews. But will be more difficult with the Apple AppStore and Windows Store. We have to improve our application usability to be accepted in the store. We can use a professional template from <a href="https://market.ionic.io/"><em>Ionic Market</em></a> an official <em>Ionic market</em> for starters, plugins, and themes. Now we will describe the steps that should de follow to publish the app in all three stores.</p><h4>Google Play Store</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*peQf9Q-7R7YzZqhY7yzSMg.png" /><figcaption>Google Play Store</figcaption></figure><p>The Android store is <a href="https://play.google.com/store">Google Play</a> — our application is easily accepted (in hours) on this store. There are many free applications in this store, and their users are in general not paying for apps. Will cost us $25 per life for publishing in this store and Google takes 30% of revenue. The user receives 70% of revenue.</p><p>First, we have to create a <a href="https://developer.android.com/distribute/googleplay/developer-console.html">Play Developer account</a>, and there we have to create an application and edit our <em>Store Listing</em>. <em>Title</em> and <em>Full Description</em> are important for <a href="https://blog.kissmetrics.com/app-store-optimization/">ASO</a> — be aware that around 60% of users are coming from store searches. In <em>Manage Releases</em> we will upload our <em>.apk</em> files.</p><h4>Apple App Store</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Iior1dBosksFCooAI4pFBg.png" /><figcaption>Apple App Store</figcaption></figure><p>The iOs store is <a href="http://www.apple.com/itunes/charts/free-apps">Apple Store</a> — our application is verified in detail and takes around one week to be published. We can make more money from this store, and in general, there are more payable applications than free. We pay <a href="https://developer.apple.com/">$99 per year for publishing</a> on this store.</p><p>For publishing, we need to have an <a href="https://appleid.apple.com/">Apple Id</a>. Then we have to go to our Apple developer account in the area named <a href="https://developer.apple.com/account/ios/certificate">Certificates, Identifiers &amp; Profiles</a>. There we have to create an application id. Then, we have to go to our <a href="https://itunesconnect.apple.com/">iTunes Connect account</a> where we have to request a new application using <em>New App</em> using the application identifier created in the previews step. There we have to complete <em>App Information</em> and other application data before submitting it for approval.</p><p>Also, we have to upload the binary file, and this can be done in two ways. The first option is to use <em>Product/Archive</em> option from <em>Xcode</em>. Second is using a distinct application named <em>Application Loader</em>.</p><h4>Windows App Store</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8M01Pbm9WWNdJOQ5NouNPA.png" /><figcaption>Windows Store</figcaption></figure><p>The store for Windows applications is <a href="https://www.microsoft.com/en-US/store/apps/windows">Windows Store</a> and is not so rich in applications like the previous stores. We have to pay <a href="https://developer.microsoft.com/en-us/windows">$40 for starting publishing</a> in this store. The advantage of this store is that it is a unified store for all Windows 10 applications and we can publish our application to all Windows 10 devices.</p><p>For building our app we need a Windows 10 machine with Visual Studio 2015 or 2017 installed (we can get one for free usage for one month, or we can buy one forever <a href="https://developer.microsoft.com/en-us/windows/downloads/virtual-machines">Windows 10 preinstalled with Visual Studio Community Edition</a>).</p><p>We can create the deployment artifacts in <em>Project/Store/Create App Packages</em>and there we can choose to link to an existing application definition from our <a href="https://developer.microsoft.com/en-us/windows">Windows Developer Center account</a> or to create a new one. The package will be signed automatically, and we have to upload it manually to the store using <em>Project/Store/Upload App Packages</em>.</p><p>We don’t have support in Ionic 2 for generating icons and splash screen resources like in iOs and Android using <em>ionic resources</em> command, but we can generate all the icons and splash screens using <em>Properties/Visual Assets</em> option from Visual Studio. Also, Windows 10 resources can be generated using <a href="http://wat-docs.azurewebsites.net/Tools">this online tool</a>.</p><p>For other related content please read our <a href="https://leanpub.com/ionic4">Ionic book</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4cc9bcb1e17a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ionic-book/mobile-devices-and-mobile-operating-systems-4cc9bcb1e17a">Mobile — devices, operating systems and stores</a> was originally published in <a href="https://medium.com/ionic-book">Web Native</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>