bakkenbaeck / doorbellbotnative Goto Github PK

Add something which allows us to securely store access tokens or other settings which should not be stored unencrypted - Keychain on iOS, probably KeyStore on Android.

Take Setup instructions from #3 and display them on iOS.

Hit APIs designated by @anskaal to send or receive information from Slack.

Hook up the viewModel from #10 to Android views

Set this up on a B&B account with fairly low limits.

• Allow sending of notifications to a list of iOS and Android devices
• Allow sending of silent push notifications to a list of iOS and Android devices
• Allow registration and de-registration of devices for push

Non-secure persisted settings - probably some kind of wrapper around User Defaults and SharedPreferences.

Take viewModel from #11 and create an iOS Screen with it

Setup Firebase Crashlytics on Android so we can get notified about crashes. Try to use a key from #27

Take setup instructions from #3 and display them on Android

Hit APIs designated by @anskaal to send or receive information from the modem service.

This covers setting up a basic project which runs "hello world" on iOS and Android apps using Kotlin Native. A tutorial for doing this can be found here: https://kotlinlang.org/docs/tutorials/native/mpp-ios-android.html

• Figure out what network the user is on
• Compare to stored approved networks¹
• Return whether the user is allowed to let someone in at the moment

¹ - Follow up: Where are we storing these, on the modem service?

No API keys for script kiddies! We should figure out a way to do this then document it.

• Kick the user to the Open Door screen if they tap on the push notification
• Clear push notifications if the door has been opened.

This will allow us to automatically remove notifications which no longer require action, or at least update them to note that the person was let in.

Setup Firebase Crashlytics on iOS so we can get notified about crashes. Try to use a key based on #27

Set up a view model for the various pages of instructions to get Doorbell Bot set up.

• How many pages should be on it?
• What text should be displayed?
• Is there an image which should be displayed with it?
• Is there anything the user needs to do before moving on to the next page?

• Add UI and options for admit/deny on the notification
• Send command to modem directly from the notification itself

• Add UI and options for admit/deny on the notification where supported
• Send command to modem directly from the notification itself

Initial research led to some issues with ktor, but that was before the official release of Kotlin 1.3 and the Native beta. Determine:

• Is there any way to use ktor without coroutines?
• Have the issues around using coroutines on K/N at least been cleared up to the point where they're usable?
• Is there any alternative to ktor for Raspberry Pi if neither of the above are happening?

Hook up the viewModel from #10 to iOS views

We want to use Firebase push notifications for the sake of not having to set up our own push server which can hit both iOS and Android.

• Is there a Kotlin/Native SDK for Firebase?
• Is there an HTTP way to submit push tokens which we could use from either iOS or Android?
• Is there a way to create a method which delegates to the native app itself to submit something?
• Or do we need to do this natively in each app?

Take viewModel from #11 and create an iOS Screen with it

We should try to keep localization contained within the native core.

• Does anything already exist for that?
• If it doesn't, how should we do that, particularly given that you can't really stick raw data files into a K/N shared framework?

Create a ViewModel for an Open Door screen.

• Button title to open door
• Any other copy
• Notification to dismiss if the door has been opened by someone else
• Copy for alert to user that door was opened by someone else.

Once #1 is done, set up shared networking to allow iOS and Android to GET / POST / PATCH / PUT / DELETE data easily from an arbitrary base URL.

• If we can use ktor, use that
• If not, use expect fun to set up ways to access things on different platforms.

Shared view model for settings:

• Settings names
• Settings current values
• Ability to update current value and have it persist locally

• Where should this be stored?
• How do we store this securely?
• How do we store this in a way where someone can't just rename their WiFi to an approved network's name and let people in?

• Kick the user to the Open Door screen if they tap on the push notification
• Clear push notifications if the door has been opened.