ewpatton
commented
4 years ago I’m weary of this because the whole point of MIT App Inventor is to lower the barrier to entry of making app development; having to ask app inventors to reason about the permission model is probably asking too much for most of them. Also, the permission model on Android and iOS are slightly different and we don’t necessarily want to make platform-specific allowances in the web UI as we move forward with our cross platform support.
On Oct 13, 2019, at 17:15, GOTFire notifications@github.com wrote:
Describe the desired feature We cant see permission thats needed for components.
Some components needs special permissions.Like phone component.But we cant see this permission on development.We can see this permision request when we install app to device or when we open screen that screen uses this component.
Another reason we cant idenfity which component need this special permissions.ıf our project old and big.Its hard to find it.
Give an example of how this feature would be used Maybe there is a permission tab and we can see components and requered permissionso we can try alternative components or we dont use it.
Students understand permissions on Android ecosystem.Rules/Policy etc.
Why doesn't the current App Inventor system address this use case? We cant see needed permissions for each component
No confilics Why is this feature beneficial to App Inventor's educational mission?
Its expand students view.They can see how permissions work on Android
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.
Describe the desired feature We cant see permission thats needed for components.
Some components needs special permissions.Like phone component.But we cant see this permission on development.We can see this permision request when we install app to device or when we open screen that screen uses this component.
Another reason we cant idenfity which component need this special permissions.ıf our project old and big.Its hard to find it.
Give an example of how this feature would be used Maybe there is a permission tab and we can see components and requered permissionso we can try alternative components or we dont use it.
Students understand permissions on Android ecosystem.Rules/Policy etc.
Why doesn't the current App Inventor system address this use case? We cant see needed permissions for each component
No confilics Why is this feature beneficial to App Inventor's educational mission?
Its expand students view.They can see how permissions work on Android