https://github.com/adrian-sal-kennedy/20221209-challenge

https://github.com/adrian-sal-kennedy/20221209-challenge

android xamarin xamarin-forms

Last synced: 14 days ago
JSON representation

• Host: GitHub
• URL: https://github.com/adrian-sal-kennedy/20221209-challenge
• Owner: adrian-sal-kennedy
• License: other
• Created: 2022-12-08T23:47:13.000Z (about 2 years ago)
• Default Branch: main
• Last Pushed: 2023-02-05T15:56:34.000Z (almost 2 years ago)
• Last Synced: 2024-11-14T15:14:53.753Z (about 2 months ago)
• Topics: android, xamarin, xamarin-forms
• Language: C#
• Homepage:
• Size: 657 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 1
• Metadata Files:
  • Readme: README.md
  • License: LICENSE.md

Awesome Lists containing this project

README

        
# **Challenge 1: FlyoutPage Model**

- **Xamarin.Forms app** (focus on Android)

- **MVVM pattern**

- **API 30 target (tested on my Galaxy s9 which is API 29...)**

- **Permissions asked at startup**

  - It's worth noting that Google specifically discourages this practice, but for the purposes of proving that I can indeed implement such things, it makes far more sense to do permissions the "old" way.

## Permissions

- First up (at `App.OnStart()`) we check the 3 permissions we need and if they are not granted we store each into an IEnumerable of a class that contains the permission name, description and rationale for display.

- We then ask the user for each permission, and if we get it we remove that permission from our IEnumerable.

- When the first page is navigated to via our `AppShell`, It will display those permissions we don't yet have, and present an option to ask again.

- Originally I was going to use Xamarin.Essentials.Permissions, but it mapped confusingly with the (relatively new) ActivityRecognition permission in Android.