https://kotlinlang.org logo
Join Slack
Powered by
swiftCon and flutterCon Berlin 2026 now in Confett...
# confetti
j
swiftCon and flutterCon Berlin 2026 now in Confetti as well
🎉 2
m
Unrelated question: didn't they merge FlutterCon + Droidcon + SwiftCon to make "the nextapp conf"?
Wondering if we should have a single "conference" with the content of the 3? LOL
j
Yeah, was wondering about that too
@mbonnin I guess we'd need an additional abstraction on backend....
m
We need federation for conferences 😅
all the things 1
How does droidcon handle it? I would do the same
Screenshot 2026-08-17 at 15.37.44.png
Different tracks
Not just quite actually
It's mainly tracks but with a tag
BTW spoiler alert but we might need something like this for Android Makers next year too
😮 1
Unrelated but that's a good question 🙂
b
wow, heavy
m
Yea
m
Oh, there's a react con too? Dang.
m
One conference to rule them all 🙂
Looking forward to the Ben Kadel keynote!
j
Yeah, I should add react one as well
m
Do these conferences have an official app? It'd be great if we could manage to advertise them by the conference and/or in the conference somehow.
j
Droidcon have there own as well I believe
m
Didn't touchlab do the droidcon one?
No sign of mobile app on nextappcon.com
j
this is what Claude has to say
Copy code
Right now conferences are entirely flat and siloed — each gets its own Apollo client, cache, and backend Datastore namespace, with grouping today only implicit in slug naming (droidconberlin2026, swiftcon2026, fluttercon2026). To make them a real hierarchy you'd need: a groupId/seriesId field threaded through the backend model (DConfig), GraphQL schema, and ConferenceId registry, plus client-side UI to group by it instead of just by year — but the bigger call is whether "hierarchy" means just a shared umbrella card in the picker (cheap — one new field + UI grouping) or a genuinely merged session list across droidcon/swiftCon/flutterCon Berlin (expensive — needs a new fan-out query since sessions stay partitioned per sub-conference by design).
I think the groupId approach might be good start and just some grouping then in conference list....at least for. now
I guess merged session list might be nice but think people will be mostly focussed on one of the "sub conferences"
I might take a look at just supporting grouping them visually in the picker for now
m
Why not make it a big "uber" conference? (nextapp devcon)
j
so, they had something similar in Orlando with droidcon and fluttercon in same venue......I'm not sure if intention was to create more crossover but they were still effectively 2 different conferences.....feels like having them in one combined agenda would have just cluttered things up for both groups
but I guess intention/hope is that there would be more crossover
m
If I looks at the agenda, some rooms have sessions from different conferences
Having everything in the same "conference" means I can filter on that room and see everything that's happening there
What we need is a way to filter on tags as well (if we don't have already)
j
fwiw this is draft PR for approach of adding that grouping github.com/joreilly/Confetti/pull/1859
thank you color 1
m
@John O'Reilly can you share a photo of how that looks on the app client?
j
this is initial minimal approach
👍 1
probably want to at least have location and date for group as a whoe
ok, getting further with this....next.app devCon actually does have single sessionize json feed for all the "sub conferences" and then adding list of tracks for each conference to allow UI to filter on those github.com/joreilly/Confetti/pull/1874
ok, that's merged now (and just publishing new version of android app to play store test track atm)....conferences have concept of tracks which we show in UI as a filter
not cast in stone and can evolve if doesn't work universally well
we'd ideally like to colour the tracks...
m
What if we keep treating it as different conferences like before + have a "next app conf" that has them all together?
And we make changing conferences easier? Like perhaps taping the conference title name?
I feel like most people won't ever change conferences mid-day, and that filters take a lot of space lol
j
the thing I didn't get before was that there's several sessions that are included in multiple "conferences"
for example the swift export one shown above is in both droidCon and swiftCon
and many of the agentic ones are likewise part of other tracks as well
this is Greg's explanation: "We basically used the “which other event is does you talk apply to” (i think that’s roughly the name of the field) as the primary sort. So each session is double-tagged. Once with the Primary event tag, but the same event (ex. droidCon), would have “droidCon” as the secondary tag as well. So someone could choose to just sort by “droidCon”, but they could add mobile app security, agentic coding, techlead, etc. That’s the way I would probably sort it. The easy way is to just sort using the primary event tag and that would be a simple OR sort where they only select one at a time."
🤔 1
so what I thought of as "sub conferences" really are just tags
latest version of android app is in play store (internal testing) if you want to try it out
@mbonnin do you think that would work for what you're thinking for androidMakers as well?
m
Testing here. @John O'Reilly what do you think about moving the tags above the dates? So that during the scroll they hide?
👍 1
j
yeah, that'd probably be better
hmm, so, nextappcon.com/agenda allows selecting multiple tracks at same time.....
and they show registration, breaks etc regardless of which track you use.....which I'm not currently showing....
m
Maybe that filter could be: if none is selected, show all. If one or more is selected, filter to these tags?
j
yeah, can try that too
m
+1 on scrolling the tags and bringing them back on scroll down (similar to the url input in chrome) +1 to colored tags
👍 1
j
so, have new version of app in play store (still internal) with those + other changes. How it figures out what the primary track is is still a bit hacky....looks like next.app has following which we'd need to map from in sessionize import but not sure how general this is.
Copy code
- Category group "Choose the PRIMARY event you are submitting for" (one selection) — this is the true primary tag.
- Category group "Which other events is your talk relevant for?" (multi-select) — these are the secondary/cross-listing tags.
@Marcello Galhardo I can't find message but I think you were suggesting colour coding room chips instead.....this is version taking that approach.....I think it looks better all right
👍 1
m
Yeah, that was an idea!
Thinking out loud, perhaps the stage should not be coloured... since a talk can be on the Droidcon Stage but be part of 2 or 3 "tracks" (i.e., Droidcon + Agentic), maybe there should be more tags, for each track a talk is in? And these would have the colour of the track.
➕ 1
j
yeah, that could work as well
m
Agreed.... But also, the stage names have the names of the conf inside (flutter, android, etc...)
So they are somewhat "themed"?
Either works for me.
Love the colored chips in call cases!
5 Views
Open in Slack
PreviousNext
Powered by