Mobius 2026 Autumn: mobile-development conference

About the event

Mobius 2026 Autumn was announced for 21–22 October 2026 in Saint Petersburg at the Airportcity Plaza Congress Hotel, Startovaya Street 6, building A. The official page describes a two-day conference on native and cross-platform mobile development, with in-person attendance and an online broadcast of part of the programme. Its schedule centres on engineering work for iOS, Android and Aurora applications, alongside sessions and workshops on AI, quality, performance and platform internals.

The first day’s AI development track contained several distinct problems. Yuri Dubovoy proposed exploring whether visual structural representations could help people control code generated by large language models; Vasily Usov described turning a prompt into a working prototype using design-system components and then into native code. Maxim Makedoshin’s session addressed legal risks in AI adoption, including copyright and reported cases of data leaks, while Yaroslav Andreev announced a workshop on porting a game to Aurora with an LLM agent and a set of instructions. Design, implementation and responsibility therefore appeared as separate programme topics rather than one generic AI theme.

The platform-engineering sessions named concrete layers of the stack. Ivan Milenin’s scheduled talk examined moving Android applications to HarmonyOS NEXT by translating Kotlin and Jetpack Compose to ArkTS and ArkUI with SMT solvers, in light of architectural differences. On the second day, Vladislav Tomilov’s NFC session traced electronic-document reading from MRZ, PACE/BAC and APDU through the Android NFC stack, NCI and radio frequency, including how logs and traces can help locate a TagLostException. The programme also included a talk on how overloaded meanings for null can create hidden debugging costs. These are announced examples of Android internals and cross-platform work, not claims about every platform.

The cross-platform sessions connected code sharing with the need to retain platform-specific behaviour. Anna Zharkova’s talk was to consider Swift beyond Apple systems through WebAssembly and compare the direction with Kotlin Multiplatform. Alexander Menshikov and Maxim Logunov presented an architecture for a desktop-and-mobile messenger using KMP while retaining a native SwiftUI iOS layer; Angelina Maltseva’s session concerned shared business logic for a media player with native Android and iOS behaviour. A session on Aurora described porting a real, multi-module KMP application, including libraries without Linux-native builds, possible blockers, and the choice between porting an existing interface or building a new client over a shared core. These cases expose practical trade-offs without prescribing a universal stack.

The performance programme brought together client-side measurement, interface behaviour and implementation choices. Vladislav Zyuzko’s listed session used Dart and Flutter for time-series analysis without a server, for situations where data must remain available offline. Timur Borgalinov described how the Uzum team moved from isolated fixes to a continuing mobile-performance process: checking the business value of speed improvements, finding slowdowns in user data and evaluating the effect of changes. Yaroslav Kulinich planned to demonstrate measuring power use in the MAX messenger with the Android SDK, while a VK ExoPlayer session discussed tuning the estimator, viewport and buffers to reduce playback delay. These are specific planned subjects, not guarantees that the same results apply to other products.

Quality and tracing were addressed through diagnostic scenarios. The Android observability session proposed showing how a small amount of added error information can help teams investigate increasingly complex failures. A deep-link talk connected a link opening the wrong screen with wasted marketing spend and described a process involving tests and click tracing. Another session covered modifying an App Store application: obtaining an IPA, decompiling it, patching and rebuilding it, then debugging on a device or simulator. The AI programme also listed UI-test generation and static application checks. Together these agenda items concern observability, reproducibility and real application behaviour rather than a generic inventory of tools.

Interfaces and the visual layer appeared through concrete engineering examples. Konstantin Moskalenko was scheduled to take apart the Liquid Glass system effect, recreate it with Metal, and move from its components to interactive animation and Telegram integration. A Compose session on heavy content concerned pan and zoom for large images; its published description proposed examining the causes of crashes and lag and demonstrating a route to smoother rendering. A dashboard talk about a 416-module monorepo asked whether build metrics could be trusted and how searches for slowdowns can overturn an initial assumption. These are particular problems named in the programme cards, rather than general advice about design.

People and processes were represented by sessions with defined subjects. Alyona Novosyolova and Olga Samarina announced a workshop on negotiating conflict, where participants would practise distinguishing facts from their own interpretations. Sergey Nuzhnenko described a “back-of-the-envelope” process for shaping a development task in direct work with a customer or clarifying an incomplete analyst brief. Denis Alexandrov’s talk considered changes to the developer profession through AI, economics, politics and the accelerating pace of life. The evening schedule also listed networking and an afterparty.

The official page names JUG Ru Group as conference organiser; GitVerse is listed separately as leading partner, not as organiser. Published speaker profiles name professionals from T-Bank, VK/MAX, X5 Tech, Cian, SberDevices, Uzum and other organisations. Those are speaker and profile associations, not evidence that the companies attended as exhibitors or that the named employees attended as visitors. The stated target audience includes mobile developers, architects, DevOps specialists, testers, team leads and project leads.

The online broadcast covered only part of the conference. The organiser separately marked some workshops and additional or late activities as in-person only, without a stream or recording; the general “Saint Petersburg + ONLINE” description therefore does not apply to every schedule entry. The official page also described discussions with speakers and experts immediately after talks as an in-person feature. Several rooms and parallel subjects were listed, so the useful selection depended on the topic and its access note. The site says programme content is reviewed by a committee of mobile-development experts. Its archive and gallery include earlier editions and are not presented here as documentary photographs of Autumn 2026.