Download the PHP package osenco/laravelpwa without Composer

On this page you can find all versions of the php package osenco/laravelpwa. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of osenco/laravelpwa

Informations about the package laravelpwa

Laravel (PWA) Progressive Web Application

Laravel 5.x Laravel 6.x Laravel 7.x Latest Stable Version Total Downloads License

This Laravel package turns your project into a progressive web app. Navigating to your site on an Android phone will prompt you to add the app to your home screen.

Launching the app from your home screen will display your app. As such, it's critical that your application provides all navigation within the HTML (no reliance on the browser back or forward button).

See too the Laravel PWA Demo

Requirements

Progressive Web Apps require HTTPS unless being served from localhost. If you're not already using HTTPS on your site, check out Let's Encrypt and ZeroSSL.

Installation

Add the following to your composer.json file :

or execute

Publish

Configuration

Configure your app name, description, icons and splashes in config/laravelpwa.php.

You can specify the size of each icon as key of the array or specify it:

Obs: In the custom tag you can insert personalized tags to manifest.json like this e.g:

Include within your <head> the blade directive @laravelPWA.

This should include the appropriate meta tags, the link to manifest.json and the serviceworker script.

how this example:

Troubleshooting

While running the Laravel test server:

  1. Verify that /manifest.json is being served
  2. Verify that /serviceworker.js is being served
  3. Use the Application tab in the Chrome Developer Tools to verify the progressive web app is configured correctly.
  4. Use the "Add to homescreen" link on the Application Tab to verify you can add the app successfully.

The Service Worker

By default, the service worker implemented by this app is:

To customize service worker functionality, update the public/serviceworker.js.

The offline view

By default, the offline view is implemented in resources/views/vendor/laravelpwa/offline.blade.php

To customize update this file.

Contributing

Contributing is easy! Just fork the repo, make your changes then send a pull request on GitHub. If your PR is languishing in the queue and nothing seems to be happening, then send Silvio an email.

Publish to Android Playstore

Bubblewrap is a tool to make wrapping your Progressive Web App into an Android App Bundle as easy as running a a couple of CLI commands. It does this by generating an Android project that launches your PWA as a Trusted Web Activity.

To start, create a directory for your project to live in and move into it:

Then, run the Bubblewrap command line tool to generate the configuration and Android project for the Android App Bundle you'll upload to Play:



$ bubblewrap init --manifest=https://my-pwa.com/manifest.json

Here, Bubblewrap is initialized with the location of a PWA's Web App Manifest file. This will generate a default configuration from the Web App Manifest, and start an in-console wizard that will allow you to change the default configuration. Follow the wizard to change any of the values generated by the tool.

Bubblewrap CLI wizard showing an initialization from airhorner with the domain overridden with example,.com and the start URLs overridden.

Google's Play Store requires application packages to be digitally signed with a certificate when uploaded, often referred to as signing key. This is a self-signed certificate and is different from the one used to serve your application over HTTPS.

Bubblewrap will ask for the path for the key when creating the application. If you are using an existing Play Store listing for your application, you will need to add the path to the same key used by that listing.

Bubblewrap CLI wizard asking for the location of the user’s existing signing key location and name.

If you do not have existing signing key and are creating a new listing on the Play Store, you can use the default value provided by Bubblewrap to have it create a new key for you:

Bubblewrap CLI wizard asking if the user would like to create new signing key.

After initializing your Bubblewrap project and completing the wizard, the following items will have been created:

  • twa-manifest.json - The project configuration, reflecting the values chosen in the Bubblewrap wizard. You will want to track this file with your version control system, as it can be used to regenerate the entire Bubblewrap project if need be.
  • Android project files - The remaining files in the directory are the generated Android project. This project is the source used for the Bubblewrap build command. You can optionally track these files with your version control system, too.
  • (Optionally) Signing Key - If you choose to have Bubblewrap create the signing key for you, the key will be output to the location described on the wizard. Ensure the key is kept in a safe place and limit the number of people who have access to it; it is what is used to prove apps on the Play Store come from you.

With these files, we now have everything we need to build an Android Application Bundle.

From within the same directory you ran Bubblewrap's initialization command, run the following (you'll need the passwords for your signing key):



$ bubblewrap build

Bubblewrap CLI output for building a project, asking for passwords for the signing key and showing the generation of different versions of the Android app.

The build command will generate two important files:

  • app-release-bundle.aab - Your PWA's Android App Bundle. This is the file you will upload to the Google Play Store.
  • app-release-signed.apk - An Android packaging format that can be used to install the application directly to a development device using the bubblewrap install command.

All versions of laravelpwa with dependencies

PHP Build Version
Package Version
No informations.
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package osenco/laravelpwa contains the following files

Loading the files please wait ....