I'm a developer of an extension with more than 15000 active users.
Many users ask for a sync feature.
Well, I have done some calculations and found out that each user has about 8 MB data to sync.
It is more than 100 GB.
Where they can be saved?
The extension is free and there is no way to monetize it to pay for a server.
The Google Drive does not allow to save into App Data from extensions.
Are there another ways to save user's data outside user's browser?
Google has no service to save data of its users?
You CAN save into Google Drive's appFolder from an extension. See the documentation. It has a quite comprehensive RESTful API.
Why not just just use Google Chrome's built in sync feature and use the chrome.storage API to store, retrieve, and track changes to user data?
Related
New to chrome extensions. I want to develop an extension where users can drag and drop text or urls to their extension and it automatically syncs up and displays on another user's extension. Should I be using a server to push/pull data to?
Basically: yes. Provided APIs do not give you the power to interact between users.
Chrome provides a concept of sync storage, but it's only to syncing small amounts of data between browser sessions of the same user.
You may want to use chrome.identity to avoid the hassle of making a separate login for your users.
I developed a Chrome extension, and I want to publish it privately.
Is it possible to set a download limit (number of user that can download)?
For example, I set a domain for an organization, how I set the number of allowed downloads?
Also, is it possible to know who is downloading my chrome extension?
You can't set a limit on the number of downloads, but you can explicitly list accounts if you select "publish to testers" option.
It can be a fixed list or a Google Group you manage.
So, you could set up a group and control membership yourself. That way you both limit and know who is downloading.
With any other publishing option it's impossible to my knowledge to either limit or track downloads using the Web Store only (since you mention a domain, this may be different for Google Apps domains, but I doubt it).
Alternatively, you could impose a limit/tracking in the extension itself, by requiring a sign-in in the extension (for example, with the chrome.identity API). Note that:
it's probably going to be annoying for users,
once downloaded, a tech-savvy user can modify your extension to remove any such checks unless a big chunk of your logic is server-side.
I need to make an offline browser on ios, which should persistent the specified webpages to the disk with the media resource such as image,css,js. At the same time, the offline browser should be able to download mutiple levels of the website automaticly, for example, make it download the webpage and all the pages linked in this webpage.
I've tried the ASIWebpageRequest,but it is not satisfying, and can not download muti levels.
Are there any other way to implement this perfectly?Can AFNetworing or MKNetworkKit do this?
Thank you very very much!
I'm making an extension for Google Chrome and I use code for autoupdating. This is because the extension isn't yet in Google Chrome webstore. But in a few days I will upload it to the Webstore and Google says you can use the Webstores autoupdating. But if I don't want to use that, will my app still update by my own server, like the way it does now?
Thanks in advance!!
I agree that docs are not very clear about this:
If you publish your extension using the Chrome Developer Dashboard,
you can ignore this page. You can use the dashboard to release updated
versions of your extension to users, as well as to the Chrome Web
Store.
But, I've tested it myself and your update_url setting in manifest.json will be overridden when you publish your extension via Chrome Web Store (CWS). In other words, publishing to CWS means that you can't use self hosted autoupdating anymore.
The reasons for that, that I could think of, may be as follows:
CWS wants to keep track of each extension stats (i.e. number of users using each extension)
privacy concerns (people don't want you to track them when they update extension)
security concerns (each extension update must go through CWS verification process)
If you want to track people (please don't) use Google Analytics on i.e. background page of your extension.
We have a requirement for people to be able to look at documents people have uploaded to us (mainly word, possibly some rtf) via our web app. We want the user to be able to open the docs inside the browser, but keep the original formatting and not have the need for another application (like word, acrobat etc).
We thought about using google docs to do this, there appears to be some batch uploading options to get stuff in there but does anyone know if we can use the API's to keep the user on our site without them having to login to google docs themselves, and keep them still on our website with re-directing to google docs to view them.
Cheers
There's an option to make documents public (Somewhere in Share->Advanced Options).
Using api you can get list of documents in your google docs account, you can even search em. In your app you could make a link to the document in google docs which opens in a new window. That way your user will never navigate away from your page. An alternative would be to use an IFrame, but it's considered bad practice.
A completely different approach could be to automatically generate and host a pdf each time someone uploads a file. There are scripts/programs which can do that, just call them after you receive a file.