Add Mobile Backend starter to existing project - android

I've got a Google Cloud console project, which I use for Google Play Game Services. Now I've read this article, talking about easily creating a mobile backend for your app. However, this only talks about creating a new project. I want to deploy the backend for my existing project.
Is that possible? How would I do that? Note that when I go to my project page in the Google Cloud Console, there is no "Getting Started" button, or "Deploy" button.

If you have an existing project created from cloud console, then you can deploy the mobile backend starter for it from the project page. If you are not seeing the option, then possibly, it is collapsed as below:
If you click that, you should be able to see the mobile backend option or photofeed app option, which are horizontally scrollable

Note, we have changed the UI a bit in the Cloud Console. But you can still deploy the mobile backend sample. https://developers.google.com/cloud/samples/mbs/deploy_backend

It would seem to me that as of this posting (4/10/14) the easiest way to do this is to just append /mobilesample to the main URL of your project, like so;
https://console.developers.google.com/project/half~baked-UIswitch-538/mobilesample/
From there you just click the deploy button, and you're good. At least I was good. And I have no idea what I'm doing :P

Related

how to make authentication in multiple apps using google developer console?

I want to make an android project using firebase as backend for it, the project contains multiple apps for admin,vendor,user and I know it's possible to add multiple apps in the same firebase project but is it possible to use one project and different apps in google developer console to add sha-1 for every app in it or what the best approach to implement that?

Facebook Developers Add Platform

I'm developing an Android App where I needed to use the SDK provided by FB to enable login via FB.
Everything is OK and it works, but when I went at:
https://developers.facebook.com/apps/MY_APP_ID/settings/basic/
I saw that there is a button that says "Add Platform".
My question is, why should I add a platform for my APP if I have everything done without that?
Does anyone know when I might need to use that option, in which cases?
Any information would be appreciated.
Thank you in advance.
As the comments above indicate, this is pretty much the answer (fell free to correct me):
If your application is running in different platforms, this means that you should be able to login in the same account from different platforms, then that's where the "Add Platform" comes in play.
In my case, I had an Android App where users can sign up using their FB account.
If in the future, I want to create a website application, then obviously, the users should be able to access that application with the same FB account.
In this case, I add an Website as a Platform.

Distribute Android apps within organization

I have to distribute Android apps within my organization. I have a google developer account. Below it tells to login to the admin console to enable private channel.
https://support.google.com/a/answer/2494992?hl=en
Problem -it does not sign me in as Google help states that
my.account#company.com, doesn't have an administrator but is instead managed by Google.
Requirement - So how can i get the administrator account.
Any help will be appreciated.
Regards
You can provide the .apk files directly to your organization.
Either you can allow to download a signed .apk file through a web site which will launch the install procedure or you can make an app market which provides a list of .apk files and installs them automatically, as Amazon's App Shop.
I'm not sure if Google account allows you to share app locally. But we use Hockeyapp to do the same. It works great. You can even integrate it to your app and upload the crashes too. Many other features. Take a look at this to know other solutions. It supports iOS as well as Android and offers a good user experience.
But you've to pay a bit for it. CashAnalytics is free. Do small research for yourself.
I have used crashlytics for this purpose in my last project.
It works great for beta distribution in development phase.
Also, it's crash reporting is excellent to guide you to the source code line causing crashes.

How does going live with PayPal works?

Our app uses PayPal to make personal payments for a publishing service, we're finished and in way to publish but when we got to the part of changing from Sandbox to going live with PayPal that's where things got complicated for us.
We're totally new to submitting anything to Paypal, I read the guide on this link and it couldn't be less clear on how to fill the form.
I filled the form to upload the mobile app, but we tripped with several doubts along the way, here I will list them:
our app is cross platform and we can only choose one platform, do we
have to submit both Android and iOS for revision separately? Even
though it's the same app?
we filled the form but there was nowhere to place an ipa or apk, only
a field asking for additional files like ad hoc stuff and such, how
do we submit our build for them to test?
I have to be honest, PayPal guides aren't clear and don't explain deeply many of the processes, as if we have already the knowledge of what to do, we searched the web for guides on how to go live but nothing came across our search.
We developed our app using Titanium Studio and the PayPal supports documents treat every submitted app as if they were natively developed, we are using a Titanium's module to make all the PayPal work, so we have no idea what API calls are made, apparently the module uses Adaptive API calls but we're not sure on this, we only make simple payments, do we still need to submit the app or should we be doing something else?.
As you can see we have zero experience with PayPal and while we wait for a response from PayPal and finish to pass every service we use to Production, we are trying to understand what to do with this submitting app phase.
We contacted PayPal support asking for a detailed explanation on what to do on our situation but no one has contacted us at all.
If the module is using the Adaptive Payments API then you'll need to submit the app for approval to obtain a live App ID for the Classic API's.
Login to your account at http://developer.paypal.com. Click on Applications and that will take you to a page where you manage all of your apps.
You should see "REST API apps" at the top and "Classic API apps" at the bottom. Click the link under the Classic section that says "Create and manage Classic API apps."
Then follow the steps from there.

Mobile Backend Starter Missing from Cloud Console

I wanted to try out cloud-connected Android app as per this tutorial:
https://developers.google.com/cloud/samples/mbs/getting_started
http://www.youtube.com/watch?v=v5u_Owtbfew
However after creating the project in Cloud Console I'm not seeing the panel described in step 6 with a "Deploy" button. https://developers.google.com/cloud/samples/mbs/images/deploy.png
What I'm seeing instead is a dashboard that doesn't mention the Mobile Backend Starter at all. https://docs.google.com/file/d/0B1HgSE-zL4aHMDlQTV9PaWswUUE/edit?usp=drivesdk
Is the tutorial not up to date? Where can I find a more recent one?
EDIT: This issue is resolved now - Mobile Backend Starter is available in Cloud Console again. https://plus.google.com/+StevePalacios/posts/i4L1iQ7d2XU
Here is how I found the MBS Console:
After a bit of poking around I realized that the App Engine Console (appengine.google.com) provides access to the MBS console, listed under the "Custom" heading in the left hand list of links.
BTW: I needed this to implement the solution posted here: https://stackoverflow.com/a/17495210/549510

Categories

Resources