We are using Amazon Mobile Analytics to collect app usage for Android using AWS Android sdk.
Since our application is business related we are tracking some custom events. Now we want show those custom events analytics to app user on Android device. Is there any way to get our app analytics data in the form of web services so that we can show the data to our users on Android app?
I have posted the same question on AWS forum here, unfortunately I have not got any reply.
Amazon Mobile Analytics recently released the "Auto Export" feature. This enables you to get your raw events in an S3 bucket. From there you can easily build a web service around it or simply read the raw S3 file.
http://aws.amazon.com/about-aws/whats-new/2014/12/17/introducing-amazon-mobile-analytics-auto-export/
Related
Is there a way to switch firebase analytics project on running flutter app?
Scenario: We have e-commerce web portals in few countries (each on subdomain). For each we have separate web firebase analytics projects.
Now we develop mobile app (one common for all countries). Inside app user can select particular shop. We want target events to proper analytics mobile project.
Any help appreciated.
There is not currently a way to use multiple Firebase apps with Firebase Analytics. This is a long-standing feature request - https://github.com/firebase/firebase-ios-sdk/issues/230.
Is it possible to use Google Analytics with Android Wear directly?
Meaning, can I create Trackers etc... directly in my wear app, or do I have to send the data to the handset as a proxy to the analytics service?
UPDATE: I have tried using Analytics directly from the Wearable, and so far I'm getting nothing (nothing shows up in the analytics dashboard, and there are no logs pertaining to anything analytics related).
Android Wear devices aren't directly connected to the internet so you can't use the Google Analytics API directly. You have to forward the events from the Wear device to your host device (which is connected to the internet), and that will then talk to Google Analytics.
Here's a snippet that shows you how to do that, although for a slightly different use case.
At Segment, we've developed an extension to our Android library that lets you use Analytics for a ton of tools from Android Wear. So instead of having to write your own code to forward all the events, you can just do WearAnalytics.with(context).track(...).
Disclaimer: I work for Segment, and developed the Android library above.
As per this link, using messages and data items is the only way to work with Google Analytics on a wearable.
I m new to GCM do u guys please guide me for using Google App Engine.
I want to create a signup page which registers details of users on Google server
to signup and logging the account
Is it possible to do so?
Thanks
Google App Engine is a Platform as a Service (PaaS) offering that lets you build and run applications on Google’s infrastructure. App Engine applications are easy to build, easy to maintain, and easy to scale as your traffic and data storage needs change. With App Engine, there are no servers for you to maintain. You simply upload your application and it’s ready to go.
For using App Engine you have to first download an appropriate sdk based on your development environment
Download the Google App Engine SDK
For working on a particular language
Google App Engine Languages
Your question mentions a bunch of technologies and sounds a little confused, so I'll try to summarize these different technologies. Google Cloud Messaging (GCM) makes it possible for your Android app to register itself and for your server to broadcast messages to all registered devices. Google App Engine allows you to create a web server that serves as a backend for your Android app (or as a frontend web app) hosted on Google's cloud infrastructure. Google App Engine includes a feature called Cloud Endpoints which simplifies writing a backend for Android by automating serialization/deserialization, authentication, and auto-generating an Android client library for invoking the backend functionality. Google+ sign in allows you to provide users of your application with the ability to sign into your application with their Google+ account. Google+ sign in on the web also makes it possible to provide an opportunity to install your Android app and to persist the sign-in on the installed app.
I'm trying to use Google Cloud datastore as remote data collector of a bunch of sensors, connected via an android Smartphone.
Firstly I'm trying to make it working in standard java.
The question is if it is possible to access Datastore directly from an android App of I need to build a GAE app that interact with the datastore.
I read for a while the documentation about the google api, but it is not really clear, how to use the Oauth 2.0 protocol.
Thank You all
You can use the oath2 support built into android as long as every user of the app is an admin of your google cloud project/app engine app. If you want to allow untrusted users to upload data, you would have to use your own endpoint and authentication strategy.
I have an app that has some configuration settings stored in SharedPreference. Now I want to provide a web interface using which customers can log into their account through a browser on the web and change the config settings seamlessly. These changes should be pushed to my android app..
I know C2DM is one option but I dont want to rely on :
If Google Market app is installed on my customer's app.
If they have configured a google account linked to their phone(It uses an existing connection for Google services. This requires users to set up their Google account on their mobile devices. source : http://code.google.com/intl/pl-PL/android/c2dm/)
What are my options?
For push notifications there is another one better service: Urban Airship
I guess C2DM implementation with a broadcast receiver would not be such a bad idea. SMS are costly and implementing my own notification system couldnt be more battery power efficient than google's.
My concern of customers not having Google Play or an account linked to their phone will be taken care of based on the fact that anyways they will be downloading my app from the market and that makes them have the two requirements met.