Is it possible for all android versions to create a user registration activity for maximum 2 registrations per device? I refer to using Firebase from API 23 to the latest API 32
Related
I applied user authentication with phone number in my flutter app using firebase, but the SMS with the one time password service is limited to 50 SMS/day, so I wanted to find a way to authenticate by phone number without firebase. its possible
I tried searching for ways to authenticate with phone number but all the results I found were using firebase
i'm building an app that lets users live stream and many users could be live streaming at the same time, is that possible with agora.io? I'm using the web version with vue.js.
Agora's Platform supports these features. In the SDK, each channel represents a live stream, which can have up to 17 broadcasters and 1m audience members.
The Agora SDKs allow developers to build apps that implement channels as needed. Within the Agora platform, users are matched by AppID and Channel name, so your app will initialize the engine with the AppID, and then join channels by passing in the channel name as a string. (See guide on how to join/leave channel)
Example of UseCase: I am a teacher, with this mobile device. I need to create and enable 40 students to use the app, from their userIDs which are authenticated using my mobile number, as they do not have their mobile device with them in class. They might go back home and sign in from their devices, but they might also sign in from the teacher's device. They don't want to use a password. They prefer an OTP. How can we do this?
Context:
We work with youth in the community, and need to enable many of them to sign in to an app using OTP, using the same mobile device. How can we maintain the integrity of the user's digital identity while making login easy?
The react-native app allows users to create UserIds using OTP or Facebook or Google OAuth. While we can only sign in one user per mobile device, we have the requirement to get multiple youth to sign in using one device. They need not stay signed on. OTP seems to need a single mobile number, and not multiple unique user Ids to be created with one mobile number
How can we design the backend and code such that this need can be met?
For an Android application, I am tracking active usage on both Fabric and Firebase. Since the most recent release I am noticing significant discrepancies between the number of daily active users.
From the Fabric docs I understand that active usage is defined as:
The number of unique app installations across all devices that were
active on a specific day. Note: Foreground activity must happen for a
device to be active.
Firebase groups active users based on user engagement with a minimal session duration of X seconds (typically 10 secs):
An active user has engaged with an app in the device foreground, and
has logged a user_engagement event.
A possible reason for the discrepancy could be that firebase triggers a first_open event when an app is updated which would mean that users are added that have only updated but not engaged with the app.
However, looking at user_engagement and first_open in bigquery
I can see that they provide different estimates (user_engagement exceeding first_open events). In this case filtering on user_engagement is equal to the number of active users in the firebase dashboard.
Did anybody experience similar discrepancies? I have had contact with both Firebase and Fabric but this did not resolve my issue. Importantly, it is not within a small margin of error, Firebase active users are 4-5 times bigger compared to Fabric.
I'm using twitter developer API for my project. I have created an account with my phone number and email address. As you know there are some rate limits in twitter API!
For using API I should create app and user tokens of that app.
My question is that if I create multiple apps for that single account and use them in my project, my rate limit is multiplied by number of apps or requests are aggregated so my rate limit doesn't change?
Yes. It is limited by account.
Rate limiting of the standard API is primarily on a per-user basis —
or more accurately described, per user access token. If a method
allows for 15 requests per rate limit window, then it allows 15
requests per window per access token.
See: https://developer.twitter.com/en/docs/basics/rate-limiting.html