finished the text of the third article about PWAs

content/blog/2023/web-pwa-native-Native2.md

@@ -13,7 +13,7 @@ tags:
 image:
   src: blog/2023/part2-native.jpg
   alt: |
-    ???
+    A stand of smartphones
 summary: |
   If you have an idea for a digital product,
   you may be wondering if you should build a
@@ -27,7 +27,7 @@ summary: |
 ---
 {% import 'embed.macros.njk' as embed %}
 
-If you haven't read part 1 yet, it has a great introduction to each option along with a fun comparison chart.
+If you haven't read part 1 yet, it has a great introduction to each option along with a quick comparison chart.
 [Read Intro to Responsive Web Apps, PWAs, and Native Mobile App](/2023/05/05/web-pwa-native-RWA1)
 
 
@@ -52,24 +52,24 @@ A native mobile app is an app created specifically for one particular mobile pla
 
 ### Choose a Native Mobile App when…
 ### Advanced Capabilities
-…when your project requires a high level of hardware or software integration.
+*…when your project requires a high level of hardware or software integration.*
 
 Native apps can access all of a device's hardware and software features. For example, unlike RWAs, native mobile apps can integrate directly with a specific mobile device’s GPS for geofencing, access light and proximity sensors, or use a device’s camera.
 
 ### High Performance
-…when you need advanced performance.
+*…when you need advanced performance.*
 
-Native mobile apps are optimized for a specific platform. Because of this specialization, they can provide a higher level of processing power for things like large videos or games with lots of animation compared to an RWA. This difference is especially pronounced when there is limited or no access to an internet connection.
+Native mobile apps are optimized for a specific platform. Because of this specialization, they can provide a higher level of processing power for things like large videos or games with lots of animation, compared to an RWA. This difference is especially pronounced when there is limited or no access to an internet connection. Native mobile apps are downloaded onto a specific device and can function even when there is no internet access.
 
 ### Advance Security
-…when you require advanced security.
+*…when you require advanced security.*
 
-A native mobile app offers advanced security beyond the typical HTTPS encryption available with an RWA. If you are developing a banking product or need to meet strict HIPPA requirements, a native mobile app is a better option than an RWA.
+A native mobile app offers advanced security beyond the typical HTTPS encryption available with an RWA. If you are developing a banking product or need to meet strict HIPPA requirements, a native mobile app is likely a better option than an RWA.
 
 ### Discoverable Via App Store
-…when the people you want to reach will look for your app in an app store.
+*…when the people you want to reach will look for your app in an app store.*
 
-Native mobile apps live in app stores like the Google Play Store and Apple’s App Store. If your research shows that the people you want to reach typically look for the type of content you will provide in app stores, or if they all use the same app store, or if you want to build your marketing plan around app stores, then a native mobile app is a better choice than the RWA which is not listed in app stores.
+Native mobile apps live in app stores like the Google Play Store and Apple’s App Store. If your research shows that the people you want to reach typically look for the type of content you will provide in app stores or if you want to build your marketing plan around app stores, then a native mobile app is a better choice than the RWA which is not listed in app stores.
 
 {{ embed.img(
   src='blog/2023/no.png',
@@ -81,24 +81,24 @@ Native mobile apps live in app stores like the Google Play Store and Apple’s A
 
 ### Don’t choose a Native Mobile App when…
 ### Higher Development & Maintenance Costs
-…when you want to keep short and long-term costs down.
+*…when you want to keep short and long-term costs down.*
 
 Native mobile apps require a unique codebase for each platform. For example, if you wanted to make the same native mobile app available on both Android and iOS mobile devices, you would need to build one codebase for Android and a separate codebase for iOS. Each codebase requires different proprietary technologies and likely requires separate teams of developers to build and maintain each platform. It is frequently more expensive to reach the same range of people with a native mobile app compared to an RWA.
 
 ### Lengthy Development
-…when it’s a priority to make your app available to users quickly.
+*…when it’s a priority to make your app available to users quickly.*
 
-Because native mobile apps require a separate codebase for each platform you want to support, development takes longer than it does to develop a single codebase for an RWA. Additionally, each app store has its own set of requirements in order to launch an app. These can sometimes be complex. Wait times for app store approval to publish the app or an update can be lengthy as well.
+Because native mobile apps require a separate codebase for each platform you want to support, development generally takes longer than it does to develop a single codebase for an RWA. Additionally, each app store has its own set of requirements in order to launch an app. These can sometimes be complex. Wait times for app store approval to publish the app or an update can be lengthy as well.
 
 ### Not Discoverable Via Search
-…when the people you want to reach will look for your content with a search engine.
+*…when the people you want to reach will look for your content with a search engine.*
 
-Unlike for RWAs, search engines don’t index native mobile apps. If your user research indicates that people frequently use search engines to search for the type of content you offer, an RWA may be a better choice. Alternatively, you could build a marketing website that introduces your app and links people to the appropriate app store for download.
+Unlike for RWAs, search engines don’t index native mobile apps. If your research indicates that people frequently use search engines to search for the type of content you offer, an RWA may be a better choice. Alternatively, you could build a marketing website for the search engine to find that introduces your app and links people to the appropriate app store for download. (A separate marketing website will futher increase the costs and development costs.)
 
 ### Limited Reach
-…when you want to reach a broad audience across devices.
+*…when you want to reach a broad audience across devices.*
 
-Because it takes longer and costs more to reach the same range of people with a native mobile app than with an RWA and because native mobile apps are offer less backward compatibility, the number of people who can access a native mobile app will likely always be more limited than the number of people who can access an RWA.
+Because it takes longer and costs more to reach the same range of people with a native mobile app than with an RWA, and because native mobile apps offer less backward compatibility, the number of people who can access a native mobile app will likely always be more limited than the number of people who can access an RWA. Additionally, a native mobile app is limited to mobile devices. To provide access to your content on a laptop or desktop, you would need to develop a separate native desktop software.
 
 ____
 Is a **Progressive Web App** right for your digital project?

content/blog/2023/web-pwa-native-PWA3.md

@@ -13,15 +13,28 @@ tags:
 image:
   src: blog/2023/part3-progressive.jpg
   alt: |
-    ???
+    Pen and notebook with a sketch of a website interface
 summary: |
+  If you're weighing the performance optimazation
+  and device integration opportunities
+  of a native mobile app
+  against the broad reach and lower cost
+  of the responsive web app,
+  and can't decide which is a higher priority
+  for your digital product,
+  don't despair.
+  The progressive web app may be
+  just the solution you need.
   This is part 3 of a three-part series
   unpacking the reasons to choose
   one platform over another.
   Let's explore the progressive web app.
 ---
 {% import 'embed.macros.njk' as embed %}
 
+If you haven't read parts 1 and 2 yet, you may want to start with the introduction to RWAs, PWAs, and Native Mobile Apps in part 1. There's also a comparison chart for quick reference.
+[Read Intro to Responsive Web Apps, PWAs, and Native Mobile App](/2023/05/05/web-pwa-native-RWA1)
+
 ## Progressive Web App - Best of Both Worlds
 
 > **TL;DR**
@@ -30,6 +43,9 @@ summary: |
 > advanced capabilities, you will want to investigate the
 > progressive web app (PWA) option for your app project.
 
+A progressive web app (PWA) is a responsive web app
+with additional capabilities similar to a native mobile app. Like responsive web apps, PWAs are built using standard web technologies -- HTML, CSS, and JavaScript. They are accessible from any device with a web browser such as Chrome, Firefox, Microsoft Edge, Safari, or a mobile browser. Like native mobile apps, PWAs can be included in app stores. They can provide push notifications, offline mode, and a homescreen icon.
+
 {{ embed.img(
   src='blog/2023/yes.png',
   alt='The word yes with a smiley and sparkles',
@@ -40,6 +56,37 @@ summary: |
 
 ### Choose a PWA when…
 
+### Lower Development & Maintenance Costs
+*…when it’s important to keep initial development costs low.*
+
+Just like responsive web apps, progressive web apps require just one [codebase](/2023/05/05/web-pwa-native-RWA1/#choose-an-rwa-when%E2%80%A6) to be available on any device with a web browser. From a single codebase, a PWA can reach people on any device with a browser, making it less expensive to develop and maintain than a native mobile app which requires unique codebases for each device. Depending on the amount of special capabilities you need to add, a PWA can cost a bit more than an RWA.
+
+### Faster Development & Updates
+*…when it’s a priority to make your app available to users quickly.*
+
+PWAs have all the same advantages of RWAs when it comes to speed of development and updates. Developing only one codebase takes less time than developing separate native mobile app codebases for each device. Updates require fewer specialized technologies and can be done incrementally. On the other hand, packaging your PWA for inclusion in app stores takes more time, then a simple RWA, and requires going through the app stores approval process.
+
+### Discoverable Via Search Engine & App Store
+*…when the people you want to reach will look for your app with a search engine and in an app store.*
+
+If your user research shows that people search for the type of content you offer in app stores *and* via web searches, the PWA can help you reach all those people more effectively than either an RWA -- which isn't available in app stores -- or a native mobile app -- which doesn't appear in web searches.
+
+Since PWAs are a type of web app, search engines like Google will automatically index them and include them in search results. Various tools such as PWABuilder essentially wrap up a PWA like a native app for inclusion in the Google, Apple, and Windows app stores.
+
+### Broad Reach
+*…when you want to reach a broad audience across devices.*
+
+If budget allows, PWAs can reach a broader audience than either responsive web apps or native mobile apps. With a single codebase, people can access the RWA on any device with a browser. They can find it from a search engine and, with some extra packaging, in any app store. They can access a PWA via the internet or download it onto their phone like a native mobile app and use it offline. Like RWAs, PWAs take advantage of the web's high level of "backward compatibility," meaning people on older devices will have some level of access.
+
+### Specialize Capabilities
+*…when you want to reach a broad range of people while keeping costs down as much as possible, but need some specialized capabilties.*
+
+PWAs are better than native mobile apps and RWAs at providing a balance between reach, cost, and specialization. If you need to be able to send alerts or "push notifications" to people even when they do not have the app open on their phone, PWAs can offer that just like native mobile apps, whereas RWAs cannot.
+
+If you cannot afford to build and maintain more than one codebase, but people using your app may have limited or sometimes no access to the internet, a PWA is likely the best option. While it may not perform as seamlessly as a native app without internet access, people can download a PWA onto their phone and access the content without a wifi or data connection.
+
+To access and RWA, people need to open a browsers, but people can access a PWA via an icon on their phone's homescreen just like they do with a native mobile app.
+
 {{ embed.img(
   src='blog/2023/no.png',
   alt='The word no with a frowning face',
@@ -50,7 +97,13 @@ summary: |
 
 ### Don’t choose a PWA when…
 
+In a nutshell, if your budget and timeline is quite constrained and you don't need any special capabilities, then the best option would be to build a responsive web app instead of a PWA. After you have more information about what the people using your app want and you have additional budget, you can always turn the RWA into a PWA. On the otherhand, if you do have plenty of budget and highly specialized needs that require full integration with a specific mobile device, a native mobile is going to be a better option than a PWA.
+
+## You Made It!
+Thanks for joining this epic journey to dig deep into the responsive web app, progressive web app, and native mobile app platforms. If you have questions about anything you read here, please feel free to ask us. We have a [handy dandy contact form](/contact/) you can use or you can chat with us on [Mastodon](https://front-end.social/@OddBird).
+
+If you've decided that an RWA or a PWA are the right platform to build your digital product, we specialize in designing and developing those two types of apps at OddBird. Check out our [past work](/work/) and [let's chat](/contact/). If you've determined that a native mobile app is what you need, please let us know, and we can help refer you to experts in your mobile platform of choice.
 
 ____
-Still not sure which platform is right for you digital product? Go back and review the **comparison chart** while you muse.
+Still not sure which platform is right for your digital product? Go back and review the **comparison chart** while you muse.
 [Responsive Web App vs PWA vs Native Mobile App Comparison Chart](/2023/05/05/web-pwa-native-RWA1/#what-are-rwas%2C-pwas%2C-and-native-mobile-apps%3F)

content/blog/2023/web-pwa-native-RWA1.md

@@ -13,7 +13,7 @@ tags:
 image:
   src: blog/2023/part1-web.jpg
   alt: |
-    ???
+    spider web with dew drops
 summary: |
   The decision of what platform
   to build your app with
@@ -79,29 +79,29 @@ An RWA is essentially a website that resizes and rearranges its content – resp
 
 Responsive web apps use a single “codebase.” The term “codebase” is developer speak for the collection of code used to build an application. Compared to native mobile apps, RWAs are relatively inexpensive to develop, requiring just one codebase to be available on any device with a web browser.
 
-To be clear, building any kind of app is not a low cost endeavor. Even a very simple responsive web app can have a price tag of $10K, and very complex web apps, such as social media platforms or project management software, cost many millions of dollars to design, develop, and maintain.
+To be clear, building any kind of app is not a low cost endeavor. Even a very simple responsive web app can have a starting price of $10K, and very complex web apps, such as social media platforms or project management software, cost many millions of dollars to design, develop, and maintain.
 
 </div>
 
 ### Faster Development
 *…when it’s a priority to make your app available to users quickly.*
 
-RWAs take less time to build, relative to Native Mobile Apps; it only takes one codebase to reach any device with a browser. It is also easier to make the minimum viable product (MVP) available to an initial set of users, get feedback, and release frequent, incremental updates.
+RWAs take less time to build, relative to native mobile apps; it only takes one codebase to reach any device with a browser. It can also take less time to make the minimum viable product (MVP) available to an initial set of users, get feedback, and release frequent, incremental updates.
 
 ### Less Maintenance
-*…when it’s you need to keep ongoing maintenance costs low.*
+*…when you need to keep ongoing maintenance costs low.*
 
 RWAs require less time and expense to maintain compared to native mobile apps. An RWA’s single codebase is built with standard web technologies, and doesn’t require an update of the entire app to make incremental improvements. It also takes less time and fewer developers to update a single codebase than to update separate codebases that use specialized technology for multiple platforms.
 
-### Discoverable Via Search
+### Discoverable Via Search Engine
 *…when the people you want to reach will look for your content with a search engine.*
 
-Search engines, like Google, “crawl” the web looking for keywords and other information to sort and rank the content. Then they collect, process, and store a database of all that content. This is called “indexing.” RWAs live on the web, so unless code is added to prevent it, they will automatically be indexed and appear in organic search results.
+Search engines, like Google, “crawl” the web looking for keywords and other information to sort and rank the content. Then they collect, process, and store a database of all that content. This is called “indexing.” RWAs live on the web, so unless special code is added to prevent it, they will automatically be indexed and appear in organic search results.
 
 ### Broad Reach
 *…when you want to reach a broad audience across devices.*
 
-People can access the same RWA on any device from a small iPhone to an Android tablet, from a MacBook laptop to a giant Windows desktop, unlike Native Mobile Apps which are limited to supported mobile devices. Additionally, the web provides a high level of “backward compatibility,” meaning RWAs can be available in some form even on old devices. On the other hand, one platform update can totally block a device from accessing a native mobile app.
+People can access the same RWA on any device from a small iPhone to an Android tablet, from a MacBook laptop to a giant Windows desktop, unlike native mobile apps which are limited to supported mobile devices. Additionally, the web provides a high level of “backward compatibility,” meaning RWAs can be available in some form even on old devices. On the other hand, one platform update can totally block a device from accessing a native mobile app.
 
 {{ embed.img(
   src='blog/2023/no.png',
@@ -125,7 +125,7 @@ If a person has a slow internet connection, they will have trouble accessing RWA
 ### Security Limitations
 *…when you require advanced security.*
 
-If your project needs advanced security beyond typical HTTPS encryption, such as in banking applications, an RWA is not likely able to meet those requirements.
+If your project needs advanced security beyond typical HTTPS encryption, such as with banking applications, an RWA is less likely able to meet those requirements.
 
 ### Not Discoverable Via App Store
 *…when the people you want to reach will look for your app in an app store.*