Dynamic start_url

Hi,

While I’m at it, I would like to expand my question : would it be possible to generate almost the whole manifest dynamically ? Like that, the start_url, app name and icon could be changed for each user. I’ve seen ways it could be done on the web (like for example on https://medium.com/@alshakero/how-to-setup-your-web-app-manifest-dynamically-using-javascript-f7fbee899a61), but I still would like to use your plugin for practical purposes. Could this kind of thing be done with PWA for wp ?

Thanks for your help !

Hi,

Thank you for reaching out to us. Regarding your first question, we do have an option, but we need more clarity on the exact output you’re looking to achieve. Could you please share a demonstration video or a reference screenshot to help us better understand your desired result? Also, please provide the URL where you need assistance.

Hi,

Thanks for reaching back. I don’t have a demonstration video (I haven’t installed the plugin on the website yet), but here is the idea :

• A user would arrive on a specific page, let’s say https://mysite.com/building/building-A/. We are sure of that, because the access to the pages is through QR codes. But there are several pages like this one : there’s building-A, building-B, and so forth.
• On that page, some data is stored in local storage with javascript, including the url, and a couple of other things (basically some elements for css personnalisation that impact the look of the rest of the website/webapp, defined throught ACF). I also want to define, through ACF, a custom icon and a custom name for the app.
• I would like the install prompt to be on these pages (building-A, building-B…) only. The idea is that if the user that arrived on https://…/building-A installs the webapp on his home screen, the start_url in the manifest would be https://mysite.com/building/building-A/, the app name (“Building A”) would be the string defined through ACF for that page, and the icon would be the icon defined through ACF for that page (these last two can be retrieved and put in local storage too). Ideally, the elements for css personnalisation in local storage would also be transferred (but that might not be necessary, since if the user opens the webapp on the building-A page, the necessary data should be re-stored in local storage anyway).
  But if a user arrives on the building-B page, then his start_url should be https://mysite.com/building/building-B/, the app name would be “Building B”, and the icon would be the one defined through ACF for the building B page.

I hope this explanation is clear enough ?? That is what I would like to achieve. Another potential option is to have a static manifest page for all users (even though I would prefer to adjust the app name and icon), but that as soon as they open the app they are redirected (through javascript for example) to the right page (which would imply that the url stored in local storage is transferred during the installation process, and I’ve read that it is not the case on iPhones…)

Could this be done with PWA for WP ?

Thanks for your patience !

Hi, we are currently checking this concern and will provide you an update soon. We kindly request your patience in the meantime.