About ReactFoo Mumbai
- Latest features of React
- Webpack, GraphQL and Apollo
- React Native
- Front-end workflows and design systems
- CSS and React
ReactFoo Mumbai is a single-day event with full-length and crisp talks, and Birds Of Feather (BOF) sessions on how to grow your career as a front-end engineer, and on state management.
On 27 May, we are hosting a hands-on workshop on GraphQL and Apollo conducted by Kiran Abburi. Workshop tickets have to be purchased separately.
Who should attend
- JS engineers from enterprises.
- JS engineers from startups.
- Cross-platform mobile developers.
- Front-end engineers.
Why you should attend?
- To learn from and network with peers from the industry.
- To gain insights from case studies of practical implementation, and evaluate ReactJS and React Native for your work.
- To program better with React and React Native.
If you are attending ReactFoo Mumbai, submit a flash talk – of 5 mins – about a project you are working on or a tool you have discovered and that you’d like the community to benefit from.
ReactFoo Mumbai conference – 26 May 2018 at ISDI DICE, Lower Parel, Mumbai.
GraphQL and Apollo workshop – on 27 May 2018 at Endurance International, Goregaon, Mumbai
For more information about speaking, ReactFoo, sponsorships, tickets, or any other information contact email@example.com or call 7676332020.
Event website: https://reactfoo.in/2018-mumbai/
Why GraphQL: A React Developer's Perspective
The hype around “GraphQL is better than REST” can be justified purely by the amount of tooling around it. With code generation, query validation, editor autocomplete coupled with an API Explorer, the life of a frontend developer has never been easier. This talk will explore Why GraphQL is awesome from a React developers perspective!
Before we go deep into
Why GraphQL and how it makes the life of a React developer easy, we will have a brief of what it is:
GraphQL is a query language that allows you to describe your data requirements in a declarative way. The shape of your request matches the shape of the response. The endpoint is always the same (Whaaat!). Let that sink in. I already feel that’s less code to be written. GraphQL is not just a tool, its a standard.
By leveraging the type system, GraphQL makes it easy to work with developer tools enhancing productivity. In a typical REST API integration with your frontend, most of the following isn’t straightforward or not possible at all.
API Explorer (GraphiQL)
Reduced Boilerplate for State Management
With caching and relay/apollo client’s state management, there’s so much less boilerplate code that needs to be written. You probably can get away without using Redux. It’s all intuitive with better handling of state.
As product requirements change, the frontend developer is less tied to the backend team for changing what data they want to display on the UI, unless there is a schema change required.
I’m an Application Engineer at Hasura, with areas of interest spanning around React, Node.js, Python, PostgreSQL, Docker, Kubernetes.