JSFoo: VueDay 2019

A day spent discussing Vue.js, developments in the Vue ecosystem and component architecture

Vue, I choose you! Reasons why Flock chose Vue.js as it's go-to framework to build apps in the Flock ecosystem

Submitted by Divyam Rastogi (@divyam) on May 30, 2019

Section: Crisp talk (20 mins) Technical level: Beginner Status: Confirmed & Scheduled


An experience talk as to why a majority of the the Flock Apps in the App ecosystem are built with Vue.


Problem statement:
1. Introduction to the Flock App so as to understand why we have something called app-integrations.
2. We have multiple mini-applications and integrations with Flock. For e.g. Google Calendar integration with Flock is an app, To-Do is an app and so on.
3. I will be highlighting the benefits of using Vue.js for building multiple apps quickly and efficiently.
4. A case for Vue CLI 3 will be made for building apps and libraries.



Speaker bio

I am Divyam Rastogi, a Frontend Developer at Flock. I have about six years of experience in Frontend development, and I’ve worked upon a variety of JS frameworks like Backbone, AngularJS, Angular, React and Vue. I’m a Vue fanboy and don’t shy away from admitting it.

Profile: https://javascriptbit.com/profile/




  • Abhishek Balaji (@booleanbalaji) 12 months ago

    Hi Divyam,

    Thank you for submitting a proposal. We need to see detailed slides and a preview video to evaluate your proposal. Your slides must cover the following:

    • Problem statement/context, which the audience can relate to and understand. The problem statement has to be a problem (based on this context) that can be generalized for all.
    • What were the tools/frameworks available in the market to solve this problem? How did you evaluate these, and what metrics did you use for the evaluation? Why did you pick the option that you did?
    • Explain how the situation was before the solution you picked/built and how it changed after implementing the solution you picked and built? Show before-after scenario comparisons & metrics.
    • What compromises/trade-offs did you have to make in this process?
    • What is the one takeaway that you want participants to go back with at the end of this talk? What is it that participants should learn/be cautious about when solving similar problems?

    We need your updated slides and preview video by Jun 20, 2019 to evaluate your proposal. If we do not receive an update, we’d be moving your proposal for evaluation under a future event.

  • Zainab Bawa (@zainabbawa) Crew 9 months ago

    Hi Divyam,

    I looked at your slides this morning, and here are my comments:

    1. There are two parallel stories in the talk – your story as a developer and Flock’s story about why Flock chose Vue. You have to collapse this, as in, put Flock’s story above everything else, and mention yourself as being the key decision-maker for Flock, given the context.
    2. Start with Flock’s problem statement to get over your initial nervousness. Instead of emphasizing your experience to justify’s Flock’s decision to go with Vue, show examples and metrics from previous organizations you have worked with, and Flock (with performance, etc) and how different frameworks compare on these criteria. What is Vue’s win on these metrics, and where does Vue not help on these metrics?
    3. Simply explain the before situation with the Flock app – ‘before’ being before you used Vue. What was the state with Flock’s app? What had you or your predecessors tried with Flock app before the migration to Vue? What was working and what was not working?
    4. My last suggestion is to be honest with your conclusions. Many a times, developer teams make decisions to switch to tech/frameworks without a scientific reason and/or owing to resource constraints. It’s ok to admit this because most of us are in such a situation.

    Look forward to your revised slides.

Login to leave a comment