Just wondering why the sessionize module was configured as a Multiplatform Module. It seems to me that it could simply be a normal android application. Is there any special reason for this?

When trying to runs with ./gradlew build (based on IOSDEV.md steps no. 5), the ktlint works as expected (failing if there's file violate the rules), due to a lot of file violated, I'm commenting the ktlint plugin, and re-run the ./gradlew build afterwards following error happened:

> Task :shared-ui:compileKotlinIosSimulatorArm64 FAILED
e: /root/DroidconKotlin-Mobile/shared-ui/src/commonMain/kotlin/co.touchlab.droidcon/ui/settings/PlatformSpecificSettings.kt: (7, 21): Expected function 'PlatformSpecificSettingsView' has no actual declaration in module <Droidcon:shared-ui> for Native
e: /root/DroidconKotlin-Mobile/shared-ui/src/commonMain/kotlin/co.touchlab.droidcon/ui/util/Dialog.kt: (6, 21): Expected function 'Dialog' has no actual declaration in module <Droidcon:shared-ui> for Native
e: /root/DroidconKotlin-Mobile/shared-ui/src/commonMain/kotlin/co.touchlab.droidcon/ui/util/LocalImage.kt: (7, 21): Expected function '__LocalImage' has no actual declaration in module <Droidcon:shared-ui> for Native
e: /root/DroidconKotlin-Mobile/shared-ui/src/commonMain/kotlin/co.touchlab.droidcon/ui/util/NavigationBackPressWrapper.kt: (6, 21): Expected function 'NavigationBackPressWrapper' has no actual declaration in module <Droidcon:shared-ui> for Native
e: /root/DroidconKotlin-Mobile/shared-ui/src/commonMain/kotlin/co.touchlab.droidcon/ui/util/RemoteImage.kt: (7, 21): Expected function '__RemoteImage' has no actual declaration in module <Droidcon:shared-ui> for Native

This fixes the padding issues on the session blocks. When you have a time slot with multiple sessions they all ran together. This fixes #160

| Before | After | | ------------- | ------------- | | | |

Hi

I am trying to build and run the iOS app, and got two errors on running ./gradlew build. The first related to failure to find sessionize/app/release.jks, so I created that.

Following that was a failure to find co.touchlab.sqliter:sqliter:0.1.1-k1.3.0-a6, this could not be found in any of the repositories.

I assume this needs to succeed before I can build the iOS app in Xcode, because the Run Script phase there is looking for the folder sessionize/lib/build/xcode-frameworks.

Is there a missing repository for sqliter library?

Hello, whilst building the android project, I get this error:

Could not resolve com.squareup.sqldelight:gradle-plugin:1.0.0-kn0.9.1-a2. > Could not parse module metadata https://dl.bintray.com/touchlabpublic/kotlin/com/squareup/sqldelight/gradle-plugin/1.0.0-kn0.9.1-a2/gradle-plugin-1.0.0-kn0.9.1-a2.module > Unsupported format version '0.3' specified in module metadata. This version of Gradle supports format version 0.4 only.

I ran the command ./gradlew generateSqlDelightInterface too.

Any ideas how to solve it?

Scroll sessions list, click into a session, click back. No problem. Click into a session, click rsvp, then back, and we lose position.

I suspects the database flow updating data, and that wipes the state.

Tested on ios

When I restart the phone, or turn internet on/off, not sure, but I've seen multiple notifications for all my talks come up days after the event. This happened about 3-4 times since 29 Oct.

Here's the last instance:

Hi, first of all thank you for this library!

But I have a question, is there any way to get data from Firestore without callbacks? Are you thinking to develop it?

getFirebaseInstance()
                .collection("sponsors-sf-2019")
                .orderBy("displayOrder")
                .get_()
                .addListeners(...)

Assume this is when selecting different bottom nav, going back to the schedule resets all. Should probably implement a more standard nav control. Possibly try out the jetpack nav thing?

Add a new navigateTo function that allows for transition animations. Use the new navigateTo function when clicking a session from schedule.

Fixes #15

• Please add the "Droidcon" topic to this repo. https://github.com/topics/droidcon
• Looks like https://github.com/droidcon/conference-mobile-app should be archived and README.md and project description updated to point here.

I'd like to see if we can save our rsvp's to a user account so if you log in on a different device, you don't lose your settings.

I think the simplest solution would be to:

1. Add login with gmail to the Droidcon app
2. With that user info, push a list of session id's to firebase/firestore. We can alternatively do this on our backend server. To discuss.
3. Whatever place we keep the list, it should be a list and a "last update" timestamp. On app start, if logged in, check and see if that timestamp is newer than our last sync (we should keep last sync in internal settings). If newer, update our local values.
4. As the user is selecting sessions, we should push values to our central store (but also update the local last sync value so we don't overwrite our own changes).

It's a very basic sync algorithm. We can iterate on it a bit if needed. It's OK if we don't get perfection. This should be relatively rare.

*copied from internal tracker Old versions of the app used to be able to listen for events sent from Firebase cloud messaging. I'd like to add that back into the app. The messaging should only really do 2 things.

1. Tell the app to update the schedule. We may have made schedule changes on the sessionize server and we want the app to run the update now. This won't show anything to the user. It'll just tell the app to do something.

2. Admin message. Just a text string that will show up in the app. Just in case there's some announcement the conference organizer would like to send out.

We manually create local files which are bundled with the apps and used until the remote schedule can be loaded. Right now those files are created manually with a script. It could be helpful to automate this as part of the build process.

Initial idea, open to adjustments as I'm not sure what will be ideal:

• Create a gradle task which runs the update script
• Make build tasks depend on new gradle task
• Add the ability to skip this task if we don't want the file to update (if we are using test schedules for example)

Is this too often? do we want to do it only before publish? Are there any risks?