{{ page.title | escape }}
8 |
11 | {{ content }}
12 |
13 |
14 |
12 | {{ content }}
13 |
14 |
3 |
4 | 
5 |
6 |
7 |
23 |
5 |
6 | Page not found :(
23 |The requested page could not be found.
24 |
5 |
6 |
46 |
47 | Page not found :(
89 |The requested page could not be found.
90 |
46 |
47 | This is the base Jekyll theme. You can find out more info about customizing your Jekyll theme, as well as basic Jekyll usage documentation at jekyllrb.com
79 | 80 |You can find the source code for Minima at GitHub: 81 | jekyll / 82 | minima
83 | 84 |You can find the source code for Jekyll at GitHub: 85 | jekyll / 86 | jekyll
87 | 88 | 89 |
48 |
49 |
48 |
49 | In the Publish PWA step of the builder wizard, locate the iOS Polyfill section and click the Download button. The app package will be generated and downloaded to your local drive.
91 | 92 |
48 |
49 | At this time you can not build the Windows 7 app via the PWA Builder Web Site, so you’ll need to build this app via the CLI tool.Windows 7 apps are supported in the Win32 platform module for pwabuilder.
89 | 90 |npm install -g pwabuilder
pwabuilder platform add win32 pwabuilder-win32
pwabuilder https://btdj.azurewebsites.net/ -d C:\Projects -l debug -p win32.
| Parameter | 112 |Description | 113 |
|---|---|
| -d | 118 |the directory you would like to generate the app | 119 |
| -l | 122 |the log level of the CLI | 123 |
| -p | 126 |the platforms to build | 127 |
48 |
49 | Given that not every platform or browser runs PWAs yet, the builder provides polyfills for platforms that lack support like iOS, Mac and Windows 7. 89 | In case of Android, PWAs are available through the browser; however, you can generate an Android polyfill app that can be also submitted to the Play store.
90 | 91 |
48 |
49 | You can easily test a PWA on any Windows 10 Machine by creating a package and sideloading it.
89 | 90 |Make sure your PC is in “dev” mode. Go to “settings > Update & Security > for developers” and then put device in dev mode.
95 |Go to pwabuilder.com and enter your site URL.
98 |On step 3 of pwabuilder.com click “download”
101 |open the “Windows 10” folder and right click on the powershell script called “test_install.ps1” and follow the prompts
104 |Open your start menu / start screen and look for app in “recently added” or search for the name from your manifest.
107 |Join the insiders program at Windows Insider
115 |Check for updates on your PC until insider updates load.
118 |Follow above instructions but use preview.pwabuilder.com.
121 |
48 |
49 | At this time you can not build the MacOS app via the PWA Builder Web Site, so you’ll need to build this app via the CLI tool. MacOS is supported in the macOS platform module for pwabuilder.
89 | 90 |npm install -g pwabuilder
‘pwabuilder platform add mac pwabuilder-mac’
101 | 102 |‘pwabuilder https://btdj.azurewebsites.net/ -d C:\Projects -l debug -p mac’
107 | 108 || Parameter | 112 |Description | 113 |
|---|---|
| -d | 118 |the directory you would like to generate the app | 119 |
| -l | 122 |the log level of the CLI | 123 |
| -p | 126 |the platforms to build | 127 |
Note if you would like to submit the app to the mac store, continue on with step 4 and 5
132 | 133 |You’ll need to download and install Xcode
136 |Then, you can follow the Submitting Your App to the Store steps in the Apple’s App Distribution Guide.
139 |
46 |
47 |
48 |
49 | In order to build a Progressive Web App, the following minimum requirements should be met:
89 | 90 |Secure. A secure connection (HTTPS) over your site makes sure all traffic is as safe as a native app. A secure endpoint also allows the service worker to securely take action on the behalf of your app.
93 |Standard Manifest. The site should be controlled by a W3C manifest that determines the experience and behavior of your PWA. This includes everything from images, to language, to the start page of your web app.
96 |Network Independent. The Progressive Web App should have a mechanism (e.g. through a service worker) to help control traffic when the network isn’t there or isn’t reliable. The app should be able to work independent of network.
99 |Responsiveness. The site should be responsive on tablets & mobile devices.
102 |Cross-Browser. The site should work in multiple browsers (e.g. Chrome, Edge, Firefox and Safari).
105 |Deep Linking. Each page of the site should have an unique URL (individual pages are deep linkable via URLs e.g. to share on social media).
108 |The quick start will provide the tools to address some of the above requirements, like building the W3C manifest and enabling network independence. However, it is responsibility of the site developer to fulfill the other requirements.
112 | 113 |