As of now, this crashes on line 32 of Speaker.swift with the following error:

fatal error: 'try!' expression unexpectedly raised an error: Error Domain=io.realm Code=10 "Migration is required due to the following errors:
- Nullability for property 'twitter' has been changed from false to true." UserInfo={NSLocalizedDescription=Migration is required due to the following errors:
- Nullability for property 'twitter' has been changed from false to true., Error Code=10}: file /Library/Caches/com.apple.xbs/Sources/swiftlang/swiftlang-703.0.18.8/src/swift/stdlib/public/core/ErrorType.swift, line 54

@NatashaTheRobot, where can I change this?

(This fixes #26)

• Delete prebuilt Realm/RealmSwift.framework for watchOS
• Update PodFile

use_frameworks!

 target 'trySwift' do
     platform :ios, '8.0' # Add `platform :ios`
     pod 'XLPagerTabStrip', '~> 5.0.0'
     pod 'Toucan', '~> 0.5.0'
     pod 'Timepiece', '~> 0.4.3'
 end

 target 'try Extension' do
    platform :watchos, '2.0'
    pod 'Timepiece', '~> 0.4.3'
    pod 'RealmSwift', '~> 1.0.2' # Add RealmSwift for watchOS
 end

• Fix acknowledgements.plist path Pods-acknowledgements.plist => Pods-trySwift-acknowledgements.plist

@NatashaTheRobot @BasThomas

One thing I noticed during the conf is I would have liked some integration between Slack and the app. Even if it were just a "go to Slack" button. Given the extent to which Slack really helps everybody keep in touch, I think that's an area to keep in mind for tying in.

https://tryswiftnyc.slack.com/archives/general/p1472998416000007

• [x] XLPagerTabStrip
• [ ] Toucan (PR available)
• [ ] Timepiece (PR available)
• [x] DynamicColor
• [ ] AcknowList (seems underway)
• [ ] HanekeSwift (seems underway)
• [x] RealmSwift

I took a stab at making the Watch app use JSON. See the branch. It needs a big cleanup and all that, but I am running into a bigger issue: I can't access the last update of the JSON file (which is stored on iPhone and not on Apple Watch). That means it throws an error here. The file path is obviously empty.

Any ideas as to how to solve this / how to sync the file to Apple Watch?

Module compiled with Swift 3.0 cannot be imported in Swift 3.0.1

is the error I am getting. It seems like the Realm and RealmSwift frameworks in TrySwiftData.xcodeproj are imported manually - and are a version (1.1.0 2) that does not support Swift 3.0.1 (see https://github.com/realm/realm-cocoa/issues/4255). I am not sure how I can manually import / update these versions, though?

cc @NatashaTheRobot

The other thing is from a speaker's perspective, I can see some value in having speaker-specific stuff somehow bundled into the app. Thinking kind of big here, but if there was some kind of login element, you could offer schedule items specific to the person using the app (e.g. meet up for technical check backstage, etc.).

https://tryswiftnyc.slack.com/archives/general/p1472998584000008

I was hoping for videos in the app, or at least links to videos. Is that already in the works? :grin:

https://tryswiftnyc.slack.com/archives/general/p1472998789000013 See also #24

It seemed that every speaker had to have a Twitter alias, even if they didn’t have a Twitter account. When a speaker’s link was actually their employer, I found that a bit confusing. Amy isn’t actually “@etsy” (or maybe she is… I’ve never seen them in the same place together… hmmm…)

https://tryswiftnyc.slack.com/archives/general/p1472998981000017

(I also expected the Twitter link under the author’s name to be a link rather than just a label; the “Follow @…” button is a little confusing, because of course it doesn’t really follow; it just takes you to their page)

https://tryswiftnyc.slack.com/archives/general/p1472998780000011