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

Srihari Sriraman

@ssrihari

REPL driven mobile development with Clojure(script)

Submitted Aug 21, 2017

The REPL provides quick feedback cycles that are necessary to keep developers in charge. Dynamic, and interactive environments that propel the development process are essential in all faces of software development, and the mobile ecosystem has recently seen an uptick here with React Native. Couple that with an inherently REPL driven language like Clojure(script), and we have a close-to-ideal environment.

I’ll speak through my experience in developing a react-native + clojurescript app (team of 2) alongside a native team (team of 10), comparing and contrasting the development and business perspectives of both teams. We finished up much before the native team, focussed on design and stability, and delivered more functional value to the business.

The talk will be most beneficial to mobile devs who crave quicker feedback cycles, and to businesses folk who want to leverage the their existing teams effectively.

Key Takeaways

  1. How were we able to build faster, and more robust apps than a native team?
    * How react native helped (will only cover contextually relevant takeaways here)
    * How clojurescript helps
    * The dynamism in process
    * Stability by design and simplicity
    * What were the anologous experiences with the native team?
  2. What does the clojurescript ecosystem look like right now?
    * what are the common reservations against picking it up?
  3. The benefits of an undivided and unilingual team
    * pros and cons of a team that does both backend and front-end
    * pros and cons of a team that uses the same language on front-end and back-end

Outline

  1. Briefly, about the company, our backgrounds, the problem statement, the teams, and the results
  2. Quicker feedback cycles enabled by react native
    • Deliver value from day 1
    • Incremental development of HTTP and websocket APIs
  3. Even quicker, continuous feedback using clojurescript
    • REPL driven development
    • figwheel. this is really cool, check it out. incremental code recompilation and loading. stays out of the way.
    • DEMO: figwheel + REPL
    • Explore and validate from day 1
  4. Stability via Clojurescript
    • seamless JS interop
    • immutable data structures by default; much easier to write reloadable code
    • makes you lean on functional programming patterns more than say typescript, which is more popular.
    • briefly compare: clojurescript, scala.js, elm, purescript, and ghcjs
    • google closure: great standard library, massive code size reduction
    • tools:
      • figwheel
      • reagent: react wrapper
      • immutable types by default, much easier to write reloadable code
      • re-frame: SPA framework
      • datascript: datalog in-memory DB
      • callback hell: CSP. Hallelujah!
  5. The Clojurescript ecosystem
  6. Reservations against Clojurescript
    • willy wonka style decisions on the movement of the language
    • lisp. very different. but hey, no precedence.
    • completely different build tooling. but then, it’s just one thing (lein).
    • personal experience from 3y ago, and contrast with now
  7. Undivided team: the pros and cons
    • loss of full picture
    • quick feedback cycles => well defined APIs
    • tradeoffs, overheads and what is realistic
    • of DB specialists and Ops specialists who existed
  8. Unilingual team: the pros and cons
    • using the source
    • at some points in time, we moved code verbatim from cljs to clj
    • ability to make PRs to the backend
    • highly coordinated backend + front-end development
    • less communication overhead

Speaker bio

Srihari is a FOSS enthusiast. He has contributed to Gimp, Eclipse, Diaspora and is excited about opportunities to give back. Over the last few years, he has written many Clojure services meeting tight latency SLAs, engineered assembly lines, written generative simulation test suites, and built performant monitoring solutions for a variety of businesses.

He has recently found a profound interest in leveraging his Clojure(script) skills for the front-end, and has delivered multiple browser and mobile applications.

He is a partner at nilenso, a hippie tree hugging bicycle riding software cooperative based in Bangalore.

Links

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