Fragments 2017

Fragments 2017

A conference on the mobile ecosystem in India

About Fragments:

Fragments is a two-day, single track conference on the mobile ecosystem in India. The conference will feature talks – full-length and crisp – panel discussions, and Off-The-Record (OTR) sessions.

We are looking for proposals in the following topics:

  1. Modern Development Practices

    • How are modern development teams structured?
    • How do you achieve cross platform design/feature parity?
    • How do your collaboration, decision making, and development processes adapt to accommodate cross platform teams?
  2. Continuous Integration/Continuous Delivery

    • How is your CI/CD pipeline designed to allow you to test, build and deploy to multiple platforms (Android,iOS,Web) simultaneously?
  3. Design

    • What tools and processes to designers follow when they have to design for multiple platforms simultaneously, given that each platform as it’s own guidelines/styles?
  4. Localisation and Accessibility

    • How do you handle localization and accessibility in modern mobile apps?
  5. Progressive Web Apps

    • Are progressive web apps the way forward?
    • Are progressive web apps a better way to solve cross platform development? What’s their future?
  6. On the ground case studies

    • Talks on how companies have changed their development workflows, processes, teams, app architecture, and tooling over time.
  7. Platform specific talks

    • We are also open to platform specific technology talks that are novel in their content or approach.

Commitment to open source

HasGeek believes in open source as the binding force of our community. If you are describing a codebase for developers to work with, we’d like for it to be available under a permissive open source licence. If your software is commercially licensed or available under a combination of commercial and restrictive open source licences (such as the various forms of the GPL), please consider picking up a sponsorship. We recognise that there are valid reasons for commercial licensing, but ask that you support us in return for giving you an audience. Your session will be marked on the schedule as a “sponsored session”.

Selection process

Proposals will be filtered and shortlisted by an Editorial Panel.

Make sure to add links to videos / slide decks when submitting proposals. We will not review proposals without detailed outlines or slide decks and preview videos.

The first filter for every proposal is whether the technology or solution you are referring to is open source or not. If you are referring to a proprietary technology, consider picking up a sponsored session.

The criteria for selecting proposals, in the order of importance, are:

  1. Key insight or takeaway: what can you share with participants that will help them in their work and in thinking about the problem?
  2. Structure of the talk and flow of content: a detailed outline helps us understand the focus of the talk, and the clarity of your thought process.
  3. Ability to communicate succinctly, and how you engage with the audience. You must submit link to a two-minute preview video explaining what your talk is about, and what is the key takeaway for the audience.

No one submits the perfect proposal in the first instance. We therefore encourage you to:

  1. Submit your proposal early so that we have more time to iterate if the proposal has potential.
  2. Talk to us on our community Slack channel: https://friends.hasgeek.com if you want to discuss an idea for your proposal, and need help / advice on how to structure it.

Our editorial team also helps potential speakers in honing their speaking skills, and rehearsing at least twice - before the main conference - to sharpen the focus of talks.

Passes and honararium for selected speakers:

A speaker is NOT confirmed a slot unless we explicitly mention so in an email or over any other medium of communication.

Selected speakers get a pass to the conference and networking dinner. We do not provide free passes for speakers’ colleagues and spouses.

We also pay an honararium of Rs. 5,000 to each speaker, at the end of their talk.

Travel grants for outstation speakers:

Fragments 2017 is funded through ticket purchases and sponsorships.
We try to provide full or partial travel grants for at least two international and two domestic speakers.
First preference in awarding grants is given to women speakers, persons of non-binary genders, and speakers from Africa. If you require a travel grant, indicate this in the field where you add your location.

Important dates:

Deadline for submitting proposals: 30 July, 2017

Conference date: 12-13 Sept, 2017

Contact

For more information about speaking proposals, contact fragments.editorial@hasgeek.com.
For tickets and sponsorships, contact info@hasgeek.com or call +91-7676332020.

Hosted by

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

Abhinandan Kothari

@abhinandankothari

Empowering Mobile Team to Harness Real Power of CI/CD

Submitted Aug 30, 2017

We at GO-JEK grew by 90,000% i.e 900X in last 18 months. Being an App Only Platform Mobile Team played a very important role in our growth as this is the only consumer facing facade that exists for us. More importantly this changed the way we work in Mobile Team, everything changed ranging from development Workflow, Processes, Tooling, App Architecture, team structure.

We were able to grow and scale our app because we were able to scale our team and the way we work. One of the Core Change response for this scale was changing our CI tool, we migrated from Jenkins to Gitlab which changed everything I mentioned above for us.
Key takeaways of my talk are how to have Happier teams, Smooth and Quality Delivery, Minimal Manual interaction and full automation, faster feedback cycles using CI/CD.

This talk is for everyone who is working on mobile team developing awesome apps as an independent developer, in a startup or an enterprise.

Outline

After mentioning the agenda of the talk, will move to the details and will explain how we improved following by introducing GO-JEK.

Development Workflow:

We are now able to harnessing the power of Single (CI/CD) tool which allows us to push the code, build it, run the tests and deploy the artifacts when everything is splendid and foolproof. We are now able to push, review and test the code, get feedback and reports and deliver on a same platform i.e Gitlab. Also, extreme automation and major enhancements were done to reduce feedback cycle.

App Architecture:

Two Monolith Repos(previously one for each android and ios) were broken into 40 repositories, neatly decoupled and published as an standalone artifact to artifactory.
All of these had their own CI/CD setup and had their own development workflow in isolation.

Processes:

Team of 40 Developers(iOS+Android+React Native) working on same CI/CD Platform helped us in solving a lot of people problems and simplified lots of processes.
Every developer was empowered to create and update his own pipeline with very simple yml syntax at gitlab-ci.yml file, which was previously tedious in the form of Groovy/Java in Jenkins world. Core Review was easier since now modulated code has changes relevant to that particular app.

Tooling:

Most of the part we needed was already part of feature set provided with Gitlab. In form of really innovative ways i.e. Gitlab Pages for sites and reports hosting, Integration with External Tools via APIs/Integrations like slack, emails and other build notifiers, deployments to artifactory and other commonly used tool set when it comes to CI.
Gitlab Runners were provisioned for all platform which will execute the build natively or on docker containers. Depending on type of the build requested.

Team Structure:

Technology specific teams(Android and iOS) were split and regrouped as Product teams - GO-PAY, GO-RIDE, GO-FOOD etc. similar to how a microservices concept is at backend.
These Product teams comprises of both Android and iOS developers dedicated to this Product. The final app is acting up as container of these products which previously hosted complete source code. Build time was reduced to less than a minutes from 50 minutes previously which improved developer productivity manifold.

Demo(Screenshots):

  • Typical Gitlab pipeline at GO-JEK
  • Understand the pipeline from .gitlab-ci.yml

Speaker bio

I am Abhinandan working as Product Engineer at Go-Jek Engineering. I am working in Android and Release engineering teams developing Android Apps along with the CI/CD setup for the iOS/Android/React-Native Apps at Go-Jek. You should attend my talk because I am the key person responsible for this change at GO-JEK as described above in my talk.
Also, I have spoken at various conferences in last couple of years:
* Droidcon Krakow 2016 - Mobile Apps Delivered Via Jenkins , Are you kidd’n me ?!!
* Flash Talk at Rootconf 2016 - Devops in Mobile World
* Rubyconfindia 2016 - Kochi on Function Testing of Mobile Apps using Appium
* Deccanrubyconf 2015 - Pune on Web Marries Ruby

Slides

https://goo.gl/P4UKRZ

Comments

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

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

{{ errorMsg }}

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

Hosted by

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