[Survey]: Phone Number Authentication for MIT App Inventor

[Black_Knight]

We appreciate your participation in this survey! Your feedback will help us understand your needs and improve the phone number authentication method for MIT App Inventor.

1. Importance of Phone Number Authentication

How important is it for you to have a phone number authentication method in MIT App Inventor?

• No need
• Probably
• Big
• Absolutely, I need it

2. Current Authentication Methods

What authentication methods do you currently use in your MIT App Inventor projects? (Select all that apply)

• Email Verification
• Social Media Login (e.g., Google, Facebook)
• No Authentication
• Other (please specify in the comments)

3. Key Features

Which features do you consider essential for a phone number authentication extension? (Select all that apply)

• Secure phone number verification
• User ID retrieval for personalization
• Account management options
• Pre-built UI elements for easy integration
• Two-factor authentication
• SMS message customization
• Brute-force protection
• Integration with backend systems

4. Ease of Use

How important is ease of use for you when integrating new extensions in MIT App Inventor?

• Not important
• Slightly important
• Moderately important
• Very important
• Extremely important

5. Willingness to Pay

Would you be willing to pay for additional advanced features in a phone number authentication extension?

• No, I prefer free solutions only
• Maybe, it depends on the features
• Yes, I would pay for valuable features
• Definitely, if it offers significant benefits

6. Budget

What is your estimated budget for purchasing advanced features in a phone number authentication extension?

• I have no budget for this
• Up to $10
• $10 - $50
• $50 - $100
• Over $100

7. Preferred Pricing Model

If you are willing to pay for advanced features, which pricing model do you prefer?

• One-time payment
• Monthly subscription
• Annual subscription
• Pay-per-use (e.g., per SMS sent)

8. Contribution to Development

Would you be interested in contributing to the development of this extension (e.g., coding, testing, providing feedback)?

• No
• Maybe
• Yes

9. Additional Comments

Please share any additional comments or specific features you would like to see in the phone number authentication extension.

[vknow360]

FSA extension already has Firebase Phone Authentication, but I don't understand why no one uses it.

[FREE] FSA: Combined features of Firebase Storage and Authentication

1. Introduction Description: This extension uses latest Firebase Storage SDK [20.2.1] and Firebase Auth SDK [22.2.0] to integrate its features in your app. You can easily do these operations: upload file download file list files delete file get metadata of files .... and all basic authentication features which includes Sign up with email & password Login with email & password Login with Google Sign In with Phone Number Get User info Update User info (Profile, Email, Password) Verify Email …

[TIMAI2]

Similar experience as @vknow360 with my "proof of concept" phone OTP method:

Firebase OTP (Sign In with Phone) using Webviewer

There have been several requests for this in the past year, but I have not seen a solution. Here, then, is one method to allow a user to sign in to Firebase (or if you want, to just authenticate their phone number). The method uses an html page and javascript, which allows for the use of a recaptcha in order to generate the verification code and send an SMS. I understand that Firebase allows for 10,000 free SMS per month (needs confirming under current requirements) I found the solution on med…

which has been available for two years. 10 likes, and only one enquiry, but I also surmise that not many have used it, possibly due to the potential security concerns with this method (which you do not mention...)

Seems most prefer federated sign ups, or plain email/password, or their own registration/login system within Firebase with no rules, although you can circumvent it to some point: Subvert FB Authentication