In a windows store app project, is it possible to send files to another user on a different device using my app, i would have my app open , send a file someway and the other user would get it on his device also with the app installed.
There isn't anything built-in to my knowledge, but you can use something like NFC, GPS, Bluetooth or a web service with user relationships to establish the link and then to send it - use something like WI-FI, Ethernet, a web service - your own or something like OneDrive, DropBox, Google Drive etc...
Related
I want to add Google Drive integration to a browser add-on I developed. Basically I want to share user settings between devices, and the settings files are too big to fit inside the 100KB limit for the storage.sync API.
But when I go to my API console and try and activate permissions for the Drive API, I get this:
Browser apps (and Android apps) aren't allowed to access app data. That's not just a warning, you actually can't continue the process until you choose a different platform. Weirdly, I can go ahead if I select "User data" (so user data is less sensitive than app data??)
What I like about app data over user data is that, if I understand correctly, app data goes in a hidden folder uniquely tied to your app, whereas user data goes in the actual user's drive. I don't want my app to have access to the broader drive, I don't want to risk messing their data up and I don't want them to see my app's config files every time they access their drive.
How can I get this "hidden folder" behavior from a browser addon?
Try the solution from this related SO post.
To be able to use your Application Data folder, request access to the following scope:
https://www.googleapis.com/auth/drive.appdata
My requirement is to associate a .exe file with a Windows Store 8.1 app. Is it acceptable to give a link through about section of the store app to a web address from where the user can download the .exe file. Will there be any problem with the certification process. Please suggest any suitable alternative if possible.
There is nothing in the Windows Store Policies that says otherwise. You can't attempt to run the *.exe file programmatically of course, but you should be fine otherwise.
Since the app is network-capable, remember to add a Privacy Policy (see here) detailing whether any user information is sent to an external website/server.
Is there any way of programmatically adding a new note to OneNote via a Windows Phone 8 app? I know I can't interact directly with the OneNote app, but wondering if there's a way to add directly to the Personal (Web) file on SkyDrive via an API or sending an email or whatever. I've done some searching and I'm guessing not, but can't hurt to ask, right?
You can connect so SkyDrive via the Live Connect API. There's a tutorial for interacting with SkyDrive from Windows Phone here. I've not tried interacting with a OneNote file but if it's on SkyDrive, it should be accessible.
Having said that, OneNote uses a proprietary format and I'm not sure if there's an API you can call on the phone to create OneNote pages programmatically. It does have an interface which you could look into but it seems you might need to do that server side and interact via a web service from your app.
I would like to build an external asp.net mvc application that has the following features:
The application is accessible via its own domain such as www.itsowndomain.com
The application has access to one Google account (such as itsownaccount#gmail.com) where all the files are stored in the Drive folder. So the users of the application should not have to log into their own Google accounts in order to access the files from this application. The application needs to have automatic access to this (itsownaccount#gmail.com)'s google Drive, that process should be transparent to the user, they should never have to authenticate themselves, its should all happen in the code in the background when the application loads.
The application will use Google Picker to list the files that are in (itsownaccount#gmail.com)'s google Drive folder.
My questions are as follows:
Is what I am trying to do possible, basically using Google Drive as a storage of files and downloading them, uploading new ones and possible editing some from an external application?
Can I use one account because all the files should be publicly available so I do not want users to have to be thinking about authentication in a site just so they can view publicly accessible files?
How do I go about implementing this, is there a tutorial because the ones I have looked at all differ as they mostly try authenticate each user with their own Google account?
you can use Google Drive as the storage solution for your application, check the Google Drive SDK: https://developers.google.com/drive/
Google Drive application usually rely on the users' accounts to store their files, but nothing prevents you from using your account to store all files and make them publicly accessible
there's an ASP.NET MVC tutorial and sample app at https://developers.google.com/drive/examples/dotnet, however, it authenticates each user with his own account. You can start from it and replace the standard OAuth flow with one that always uses your credentials, for instance, by always using a Refresh token that you generated in advance and provided to the app.
I need some light on the matter of Chrome Webstore registration.
I'm still confused despite searching through the web: the "app" will be only private for the site (we're trying to develop a Elgg plugin for our website that will allow users to access their drives).
1) for testing, do I need to register it (I did a search but some say yes like in the Google Drive SDK documentation, some say no in the google-drive-sdk tags)?
2) when the plugin is finished, tested and ready to go live for our users, do I still need to register it and pay 5$?
Thanks you for the answer you can provide us.
You don't need to register your app on the Chrome Web Store if you don't want to integrate with the Google Drive web UI: having the option to create a new file or open a file with your app directly from Google Drive.
Also, it might be easier for you not to create a Chrome Web Store listing while developing.
If you do need to integrate with the Google Drive web UI, but don't want your app to be public, you can publish your app to Trusted Testers only.