We all know that Google and Google Analytics are blocked from app users in China. But how about flurry? Can i collect analytics data from my Mobile iOS and Android App users living in China?
Flurry Analytics does work in China, on both iOS and Android.
Related
Can i collect analytics data from my Mobile iOS and Android App users living in China Mainland?
I have tried to ask this question to support but I didn't receive the answer
I have been told by Azure sales consultant (online chat) that Azure Media Services support conferencing. I cannot find such option. I see that AMS support online streaming but I'd like also to enable other people to speak.
Anyone has such experience with AMS? Is my scenario possible?
I believe you are looking for Azure Communications Services, not Media Services.
https://azure.microsoft.com/en-us/services/communication-services/
Need to configure Advertisement Insertions and Slate Images in the new Azure portal using live encoding type of Live streaming channel. Kindly help on this as i am unable to find the feature.
Ad insertions options for azure media services are described here - https://azure.microsoft.com/en-us/documentation/articles/media-services-inserting-ads-on-client-side/
"Azure Media Services provides support for ad insertion through the Windows Media Platform: Player Frameworks. Player frameworks with ad support are available for Windows 8, Silverlight, Windows Phone 8, and iOS devices."
Per Azure media Services Player documentation (https://amp.azure.net/libs/amp/latest/docs/Features.html) , Ad insertion is not supported yet at AMS player level.
It seems there is lot of overlap between features provided by both of these services:
contextually-aware smart push notifications
in-app messaging across all connected devices.
Should we prefer Mobile Engagement over Mobile Servies?
It depends on what features you want. Also, don't forget Azure Mobile Apps - an extension to Azure Web Apps (Azure App Service) that has the same mobile properties as Azure Mobile Services, but with App Service advantages.
If your needs are more in-line with enterprise usage - you need data access to on-prem or cloud SQL services, offline sync, enterprise authentication, continuous deployment, A/B testing, an associated web site that uses the same backend - then Azure Mobile Apps (Web Apps) is the right choice.
If your needs are more in the consumer / brand space - engagement analytics and in-app messaging, then Azure Mobile Engagement is the right choice.
Both have application usage statistics and push notifications.
One does not preclude the other. You could, for example, write the mobile backend and associated web site in Azure Mobile Apps and then bring in the rich engagement analytics that Mobile Engagement to your apps.
Azure Mobile Services/ Mobile Apps and Azure Mobile Engagement are both complementary technologies. Mobile Services provide push notifications using Azure Notifications Hub. Mobile Engagement provides a full 360 degree view about how your mobile app users are using the app using rich analytics and then you can create smart/specific and targeted segments using the collected analytics data. Once you have these segments, you can send both system and in-app notifications but very targeted. Hence the name Mobile Engagement. It is all about increasing your app usage, retention and monetization using smart engagement with Microsoft Azure Mobile Engagement. For more details check this link - https://azure.microsoft.com/en-us/documentation/articles/mobile-engagement-overview/.
P.S. I am a product manager on Azure Mobile Engagement services.
I'm new to all this.
When creating a mobile service on Azure and selected a DB.
How do you the the mobile service code that you download to include the data objects in the DB? I just get the TODOITEMs.
How do you used the EF with Azure and Mobile services to generate the service?
Check out this tutorial on MSDN Blogs, by Carlos Figueira from the Azure Mobile Services team.
Creating an Azure Mobile Services .NET backend from scratch
http://blogs.msdn.com/b/azuremobile/archive/2014/04/10/creating-an-azure-mobile-services-net-backend-from-scratch.aspx
There is a question below the article that asks whether this .NET back-end will work with Xamarin as well, to which the author responds: "Yes it should work with Xamarin as well"
Hope that helps!