About the conference: JSFoo is a JavaScript conference hosted by HasGeek.
Theme this year: The broad theme this year is going to be Building Reliable Web Apps. Please refer to the Topics section below for the subject of talks and workshops we are looking for.
Format
We are inviting proposals for:
Full-length 40 minute talks.
Crisp 15 minute talks.
Sponsored sessions, of 15 minutes and 40 minutes duration (limited slots available; subject to editorial scrutiny and approval).
Hands-on Workshop sessions, 3 and 6 hour duration.
Selection process
Proposals will be filtered and shortlisted by an Editorial Panel. Please make sure to add links to videos / slide decks when submitting proposals. This will help us understand your speaking experience and delivery style. Blurbs or blog posts covering the relevance of a particular problem statement and how it is tackled will help the Editorial Panel better judge your proposals. We might contact you to ask if you’d like to repost your content on the official conference blog.
We expect you to submit an outline of your proposed talk – either in the form of a mind map or a text document or draft slides within two weeks of submitting your proposal.
You can check back on this page for the status of your proposal. We will notify you if we either move your proposal to the next round or if we reject it. Selected speakers must participate in one or two rounds of rehearsals before the conference. This is mandatory and helps you to prepare well for the conference.
A speaker is NOT confirmed a slot unless we explicitly mention so in an email or over any other medium of communication.
There is only one speaker per session. Entry is free for selected speakers. As our budget is limited, we prefer speakers from locations closer home, but will do our best to cover for anyone exceptional. HasGeek provides these limited grants where applicable: two international travel and accommodation grants, three domestic travel and accommodation grants. Grants are limited and made available to speakers delivering full sessions (40 minutes or longer). Speaker travel grants will be given in order of preference to students, women, persons of non-binary genders, and individuals for Asia and Africa first.
Topics
Updated (19 April 2017): We are currently looking for talks in the following topics:
Testing: Testing tools and strategies; test driven development and testing culture; continuous integration and testing workflows; and case studies around testing your application.
Performance optimization: Performance analysis tools and techniques; best practices for building performant applications; browser, NodeJS, and framework internals; network protocols; and performance case studies.
Debugging: Tools for locating and fixing bugs in JavaScript applications; real world post-mortems of bugs that affected your organization; and using telemetry for debugging.
Immutability, type checking, and alternative programming languages: Alternatives to vanilla JavaScript; functional programming and immutability; types and type systems; and real-world case studies of introducing alternative programming languages and tools in your organization.
Build tooling: Build tools and automation, including task runners, linters, JavaScript bundlers, CSS pre- and post-processors, continuous integration tools, static analysis tools, and optimization tools.
Crash and performance monitoring: Monitoring applications for crashes and performance issues while in production.
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”.
Important dates
Deadline for submitting proposals: 15 June 2017
Conference dates: 15–16 September 2017
Contact
For more information about speaking proposals, tickets and sponsorships, contact info@hasgeek.com or call +91 76763 32020.
Note: We aren’t accepting any new talks.
Siddharth Kshetrapal
@siddharthkp
Building applications for the next billion users
Submitted Jun 3, 2017
Section: Full Talk
Technical level: Intermediate
There are 340 million internet users in India, that’s more than the entire population of the US. Sadly, 86% of them are on slow networks. These harsh conditions bring out the best architecture patterns for building performant applications.
That does not mean that the developer experience has to be terrible. Let’s talk about server rendering, loading strategies and progressive enhancement to fulfil the gold standard performance checklist without breaking a sweat.
Outline
Takeaways:
- Understand importance of performance for users + businesses
- Take-home performance checklist
- Architecture patterns that are friendly for developers + performant by default
- How can they implement these in their applications today
Outline:
-
Why should you care about performance?
1.1 Big numbers about the network spread in India (86% on slow networks)
1.2 Some scary stats about impact of performance on user behaviour + businesses -
Understand web performance nicely
2.1 How to measure performance - chrome devtools audit (lighthouse perf)
2.2 Metrics that matter
2.2 Network constraints -
What can I do to improve my application’s performance
3.1 Performance budget
3.2 Server side rendering (get to meaningful paint fast)
3.3 Un-interactive interfaces (until javascript arrives, interactions don’t really work)
3.4 Javascript loading strategies (serving the least amount, page-specific, code splitting, etc)
3.5 Lazy loading good-to-have features, analytics et al (second level of code-splitting)
3.6 Mention smaller frameworks (preact, react-lite, svelt, etc.) -
We can do even better (advanced)
4.1 2 state architecture pattern
4.2 Build static pages, enhance with javascript (progressive enhancement)
4.3 Think of each interactive component having 2 states (example in slides)
4.4 Use only static state on AMP pages and 2G and get that SEO juice. -
Cache + Prefetch
5.1 Further optimisations: preload, h2 push and what can you do with them.
5.2 Prefetch resources based on the next step in user’s journey (service worker) -
Keeping things fast
6.1 Make perf testing a part of CI builds
6.2 Test on devices+network where your audience is -
Sum up take aways for audience
Note: I purposefully do not go into the code of these to make it more audience friendly. Can add that and make it a Full talk (instead of crisp)
Requirements
Intended audience:
Folks who have built a web application or two. This isn’t very beginner friendly.
webperf fans will love this.
Speaker bio
Why should you let me talk about this/Why am I excited about it?
- I spend a lot of time during my day job thinking about (and implementing) architecture patterns for a healthcare startup in India. (It is literally my job to talk about this :D)
- I am a regular speaker at ReactJS Meetup in Bangalore. Have talked about styling, testing, performance, designing and some more
- I make OSS projects for building performant apps easier: cost-of-modules, recreate, reaqt, css-constructor.
- I obsess over interfaces, web performance and developer experience.
Links
- Github: https://github.com/siddharthkp
- Twitter: https://twitter.com/siddharthkp
- Bunch of talks from this year: https://speakerdeck.com/siddharthkp
- Video:
- Jsfoo 2016 (Flash Talk): https://youtu.be/ZKb9l9NrW8E?t=1h2m46s
- React meetup: https://youtu.be/gIinaKFZXFA?t=1h48m35s
{{ gettext('Login to leave a comment') }}
{{ gettext('Post a comment…') }}{{ errorMsg }}
{{ gettext('No comments posted yet') }}