Call for round the year submissions for Fragments in 2019

Call for round the year submissions for Fragments in 2019

Submit a proposal at any time in the year on mobile engineering, state of mobile platforms, and building products with mobile. We will find you a suitable opportunity to share your work.

Make a submission

Accepting submissions till 31 Dec 2020, 11:59 AM

##We have closed submissions for Fragments Conf, Bangalore edition which will be held on 30 March. If you wish to submit a proposal for the conference, make a submission here.

##About Fragments:

Fragments is a conference on mobile engineering, including:

  1. State of platforms/OS
  2. Hardware
  3. Engineering approaches and paradigms
  4. UX

In 2019, Fragments is a traveling conference with editions in Ahmedabad, Bangalore, and potentially Hyderabad and Kochi (in the second half of 2019).

##Topics for submission:

We seek proposals -- for short and long talks, Birds of Feather (BOF) session topics, and workshops + tutorials -- on the following topics:

  1. Deep dive technical talks on Flutter.
  2. AR Core: practical approaches and the business use cases.
  3. Reducing app size to below 10MB and how to cater for lower-end phones.
  4. PWA caching strategies.
  5. ML Kit (ML Kit | Google Developers).
  6. On device ML.
  7. Server-side ML.
  8. Progressive ML, where the fallback is on-device ML when the device goes offline.
  9. Functional programming for mobile.
  10. Coroutines in Kotlin.
  11. Mobile specific user research.
  12. Case studies from teams which have switched away from cross platform approaches.
  13. Use cases for which Native apps work versus use cases where it doesn’t make sense to build Native apps.
  14. Deep dive talks on performance.
  15. Optimising for lower-end hardware.
  16. Future of chatbots for conversations on mobile.
  17. Automating design to code.

##Contact us:

If you have questions/queries, write to us on

Hosted by

How do you make a great mobile experience? Explore with Fragments. Follow Fragments on Twitter more

ranadeep bhuyan


iOS & Android components with Flutter & reactive Dart

Submitted May 9, 2019

We will learn about Flutter, the mobile SDK released by Google and how to build components with it. It is a new way to build beautiful native mobile apps that break away from the “cookie cutter” apps that have been so common in the past. There is something far more revolutionary about Flutter is how it implements widgets that provides reactive views with Native apps as compared to the JavaScript Bridge.

Issues with React Native and Cordova such as Slow UI, unidirectional eventing, limited by browser capability, no access to native hardware capabilities will be highlighted and compared with this new approach in an architectural case study.

We will learn functional and reactive coding in Dart, which is compiled “ahead of time” into native code for multiple platforms. This allows Flutter to communicate with the platform without going through a JavaScript bridge that does a context switch. This way it addresses issues brought into the world by hybrid SDKs and frameworks.

Key Takeaways:

  • Challenges with react native and Cordova, JavaScrip bridge - how to solve it?
  • Learn developing cross platform apps with Flutter
  • Applying Material design and Cupertino components in iOS and Android apps
  • Understand Functional and reactive code with Dart


Automatic polygloting

Generating native code and compiling for a target OS - very good for Startups!
** Cupertino components on iOS
** Material design on Android
** Hands on demonstration: Conversational UI app
** Hands on Flutter app development on android and iOS app development
** Creating reusable components with Material designs and Cupertino with a flutter app that runs on Android and iOS, demo to build a conversational UI.

A side by side comparison chart with react native and Flutter.

Dart allows faster code writing and deployment. It allows building components with lesser code.
Moreover, there are a lot of fan followers and that is growing faster as it is Google that can change the paradigm of Mobile app/components development.


Not showing up in Thoughtworks Tech Radar yet, I mean it does not have a very large support community yet like JavaScript.
Everything is a widget, reactive programming is a paradigm shift for conventional sequential instruction based programming, this is instead a benefit except the change in mindset part.
30% larger binary due to its cross platform libraries - this is an opportunity of improvement

Speaker bio

Full stack engineer at Intuit. Design, develop and Architect solutions for complex engineering problems for QuickBooks customers.

QuickBooks Engineering blog


{{ gettext('Login to leave a comment') }}

{{ gettext('Post a comment…') }}
{{ gettext('New comment') }}
{{ formTitle }}

{{ errorMsg }}

{{ gettext('No comments posted yet') }}

Make a submission

Accepting submissions till 31 Dec 2020, 11:59 AM

Hosted by

How do you make a great mobile experience? Explore with Fragments. Follow Fragments on Twitter more