PWA are restricted in certain countries? Like China? - web

Are PWA are restricted in certain countries?
PWA is setup using workbox, default given in 'create-react-app'.
My managerial team says they are blocked in China.
Currently our site is using only Google Analytics apart from normal data API .
Checked my PWA site via https://www.vpnmentor.com/tools/test-the-great-china-firewall/
and its clear and can be accessed.
How can i test my PWA for the same from my own country or the client's country(USA).

Override Geolocation With Chrome DevTools
You can now override you geolocation in devtools. For more info how to do that check that google article
Custom user browser configuration
You should remember that user may have custom browser configuration. Or they may have some additional restrictions if they trying to access you site from office internet for example.
USA/China relationship
Regarding to last events it may happen that there will be no android phones in China soon. Huawei developing own os and they may not implement PWA at all.

Related

Acumatica Mobile Application Approval Error: Unsupported Protocol

We have created a customization to our site that needs approvals. When we go to the mobile application and the Approvals section, we see the item that needs approved but when we go to select the approval item, the following error pops up "Unsupported Protocol: The communication protocol used by the Acumatica ERP server to which you are trying to connect is not supported by the application. Make sure you use the latest version of Acumatica application." Our current site is running 17.206.0030. We can go to the approvals page thru the site and it works fine for the same custom approval. This error only occurs in the mobile application.
Mobile App Error Screen Shot
Last time I received the same error message in Acumatica mobile app, there was an issue with the changes, that I made in Mobile Site Map. Let me suggest to delete all Mobile Site Map customization files from the local website, restart the mobile app and try to open the Approvals screen on a mobile device.
If there will be no issues with the Approvals screen after you remove all Mobile Site Map customization files, you might consider applying different parts of your Mobile Site Map customization to determine what particular changes are causing this error. And in case of a Mobile Site Map customization built using MSDL, there is also a built-in option to enable MSDL interpreter logs, which are usually quite helpful to verify no errors have been produced by the MSDL interpreter.

Using API in Sandbox Mode on Commercial Website

I would like to display our photos posted on Instagram on our commercial web site using Instagram API.
I think that Sandbox Mode is sufficient because the number of pictures we want to display is 20 or less, but is there a regulations problem in using Sandbox for use on a commercial websites?
Also, is it necessary to switch to Live Mode?
Officially Instagram says
You do not need to submit for review for this use case. If you are a developer and you want to display Instagram content on your website, then you do not need to submit your app for review. By using a client in sandbox mode, you can still access the last 20 media of any sandbox user that grants you permission.
So actually no need to go Live mode.
P.S.
Here is the link to all cases.

I want to access full features of instagram API before go live

I want to access full features of Instagram API before go live. I am in the last phase of testing and if I submit a permission request will it be accepted? My website url will not be the same as live one as I have not migrated yet.
You cannot get full API access without getting permission review, You will be approved in sandbox mode as long as you show video screencast of ALL API usage in app.
All apps currently approved were reviewed with limited sandbox mode access, you may be able to get away without migrating to actual website, your video screencast should show all login flow and app fuctionality for all APIs and must be clear as to what your app is trying to achieve

Installing a chrome extension in China

I'm designing a chrome extension for a global market. According to Google's page (https://developer.chrome.com/extensions/hosting):
As of Chrome 33, Windows stable/beta channel users can only download
extensions hosted in the Chrome Web store, except for installs via
enterprise policy or developer mode
I understand that network admins can still configure an "enterprise policy" - but what about non-enterprise users that don't have access to the chrome web store? - and yes, I'm thinking about users in China, where the CWS is blocked.
Any clever ideas (beside asking them to use VPN :/)?
TIA!
Users may ask their friends outside China to download the installation file of specific Chrome extensions, and send to them via email or other instant chat software (QQ or others).
Or when you distribute your extensions you can attach a download url for who can not access Chrome store directly. Extensions can be installed by local file without any access to Chrome store.

Allow another developer to manage a Chrome extension/app in the Chrome Web Store

I've done plenty of searching and I can't find ANY information about having multiple developers working on a Chrome extension.
Basically, I just want to grant another developer access to manage my Chrome extension in the Chrome Developers Dashboard. (ie so that it is listed in their Chrome developer Dashboard and they can publish it/change the logo etc).
EDIT 6 Aug 2013 - The Group Publishing feature allows organisations to create a group such that the extensions can be managed by multiple developers. For more info, see Group Publishing.
Old answer
An extension in the Chrome Web Store can be managed by only one Google account.
If you want to have multiple developers manage the extension, create a Google account for your company, pay 5$ to get the right to publish and share the credentials within the company.
If you want to transfer ownership of an extension to another account, fill in this form.
Assets (screenshots) are usually not updated very often. On the other hand, it's common to update the extension's source code and description, so letting the main developer manage the extension listing makes sense.

Resources