I have created an app which has different content pages. Every page has an unique ID. I want the user to get into interaction with these pages by commenting or asking questions.
I want to have a separate google plus webpage for my app. The content in google plus does not yet exist but should get generated if a user comments a page for the first time. I also want to browse through all comments by web browser.
Is there a prefered way to do this or a tutorial for my problem? Thanks
Tata
this is probably not possible at the moment due to this limitation: Note: The Google+ API currently provides read-only access to public data. All API calls require either an OAuth 2.0 token or an API key. - okay facebook though
Related
I have a website and it is responsive to small devices also, so I wanted to publish its webview but google play store is rejecting the application by saying - "We don’t allow apps whose primary purpose is to provide a webview of a website, regardless of ownership, or to aggregate content that does not belong to the developer. To resolve this issue, please remove violating content and resubmit your app."
But I am the owner of website whose webview is used, additionally in this app push notification, QR code scanner and Geolocation functionalites are also there.
I raise the query in play store-developer but still every time they say the same thing, how to prove them that I am the owner of website whose webview is used in application.
Please someone help me, I am searching for solution on internet form last 7 days.
I also asked them how can I prove that I am the owner but they are repeating the same lines i.e - "Families Policy Requirements: We don’t allow apps whose primary purpose is to provide a webview of a website, regardless of ownership"
Please someone tell me how to prove them that I am the owner of website and please let my app get published.
Maybe you can try this. First verify your website ownership through google search console. There are two methods to verify, using dns or using url prefix. The easiest is using url prefix. Download the html file from google and upload it to your website, then use verify button.
This past week I've inundated myself with links and led myself in too many circles to count, so I thought I'd pose the question here. I have an Android app that displays webviews pointing to urls which the user must be signed in with their Google account to see (the backend is built in Google App Engine). Since the end user is likely to be signed into their Google account on their Android anyway, I'd like the sign-in process to be automatic. Currently, on the first webview the user opens up they are presented with the Google sign-in form and a really ugly subsequent page asking "would you like to allow example.appspot.com to use your Google account?"
That process is dreadful for user experience. I've seen precious few resources here and there concerning auto-login, but I'm frankly lost in the sea of almost-what-I-want-but-not-quite to be able to discern the direction I ought to be going.
I read through Nick's tutorial on authenticating an app with App Engine, but just having the token doesn't get me the uniquely-assigned user ID associated with every Google account on the backend. On top of that, prior experience has taught me the hard way that an app's webview session is incongruous with the app's HTTPClient session. So even if I could log in with Nick's method it wouldn't help me sign into the webviews.
Then I came across this tutorial, which actually seems really promising, but so far I haven't been able to adapt his code to work with my own.
I also found this SO link which suggests that all I need to do is pass the auth token (which I could presumably obtain via Nick's method) into every webview I load as a cookie.
And that's about it. They are all rather different approaches, so I'm wondering if any of them are actually what I want. Or, if somewhere out there a reasonably simple approach actually exists. I'd really appreciate it if someone knows of a straightforward answer on this one. Thank you!
For security reasons WebViews do not have access to the phone's cache, cookie store etc, it is instead recommended you use the new Chrome Custom Tabs which can auto log in your users.
Concerning the "would you like to allow example.appspot.com to use your Google account?" screen; this is the standard OAuth process and requires that the User sign in and allow your app to access their account information.
In your 'example.appspot.com' App Engine app, if you are using an API that requires user information, like the Google Calendar API, it is required that you specifically request the User for their approval to access this information.
Once you have their approval, you can then save the access and refresh tokens to make future API calls on their behalf without the need for repeated user consent. You can see how the entire Oauth flow works in the OAuth 2.0 Playground.
Even if you automatically logged your user in, they will still see the approval page requesting for your app to have access to their information. To develop a hack to forcefully approve the access to a User's information on their behalf is a major security violation.
You can take a look at the new Firebase Authentication flow to easily manage your user's Oauth experience in your App Engine application.
My current Android application allows users to signin using the Google Plus button.
A feature of my application is that i would like to reward users who return within a month of first signing in.
Do i have to remember when they first signed in using Google Plus?
Or does the com.google.android.gms.plus API expose this detail? e.g. initial Sign In date cross referenced to my Application.
I have searched the com.google.android.gms.plus docs but couldnt see anything.
Did i miss something?
I'm not aware of a G+ API that tells you when a user first authorized an application. I would recommend using Androids app data storage. That should be pretty lightweight. You can also open a feature requests.
I've successfully posted to a fan page as the actual page via the Graph API.
The problem is that the post says it was posted at "time via application name". Is there any way to hide this, so my post looks exactly as if I typed it directly into Facebook?
Any help appreciated
Short answer: No.
Slightly long answer:
Unfortunately, if such a feature was to be available, it would have to be made available by Facebook via their SDK / API. As of now, however, anytime anything is published via any third-party application, they will continue to bear the via application name stamp on their posts.
Why I say that Facebook will have to implement such a feature is because Twitter did exactly that. Sometime in mid 2012 I think. This was possibly done to bringing parity across the entire platform. * Source: http://thenextweb.com/twitter/2012/08/28/twitter-longer-displays-client-tweet-posted-web-emphasizing-first-party-reading-experience/*
I suspect this is because you can only do a limited set of actions (when posting on Twitter) as compared to the Facebook platform. On Facebook, you have several choices when posting content to the platform. Images, Videos, Links, Status updates. And I am not even counting the Open Graph actions.
You could consider filing a feature request to Facebook. If they think the suggestion merits inclusion, they just might do it.
I'm searching for a tutorial or an explanation on how to remove advertisement in my application with in-app purchase?
I will put some ads with ad-mob in my app but I also want, that the user can disable the ads when he pays a little donation. Do you know a site or tutorial where I can find a step-by-step explanation how to do this?
Or do I need to publish 2 versions of my app? One with ads and one without ads for paying?
Don't use the SharedPreferences method because if the user flushes the app data or uninstalls/reinstalls your app their ad-free status will be lost.
A couple of ideas:
If your app has any kind of web based login or authorization, you can flag the user as having bought the ad free version by updating the web database's customer data and then disable ads in code following login and verification. This has the added benefit of following the user to new devices.
Use one of the several ways to get a unique device id, and store that in a web server database. On startup, query the DB to see if the device is ad-free. See Android Unique Device ID. This will only work for that particular device though.
The two apps approach is simple enough to get the job done too. :)
This presentation seems to explain an example and includes a link to source code at github:
http://gotocon.com/dl/2011/GeekNights/Tjen_penge_p%C3%A5_Android_ARH.pdf .
It stores the purchased upgrade at a sharedpreference.
However, I'm still looking for a more secure and robust solution that works out the use-case explained here:
http://vlingo-en.custhelp.com/app/answers/detail/a_id/1785/~/moving-in-app-purchase-(ad-removal)-to-new-android-phone/p/180