PDF Archive

Easily share your PDF documents with your contacts, on the Web and Social Networks.

Share a file Manage my documents Convert Recover PDF Search Help Contact



AboutMMTLabs .pdf


Original filename: AboutMMTLabs.pdf
Author: Prakhar Goel

This PDF 1.5 document has been generated by Microsoft® Word 2013, and has been sent on pdf-archive.com on 12/08/2016 at 13:36, from IP address 202.54.x.x. The current document download page has been viewed 453 times.
File size: 447 KB (7 pages).
Privacy: public file




Download original PDF file









Document preview


About
MMT Labs short-circuits the traditional work-flow of materializing an idea into a full-fledged product
suitable for the end user. It puts you on a highway to ship your idea to the customer on the app directly by
bypassing the checks, filters and the fear of upsetting your customer. What’s more? The customer here
would willingly be trying out your ideas fully aware of the fact that the product has not passed through the
valuable QA tests, security checks and development cycles, which eases the burden on you as team and
speeds up the overall process. Upon positive feedback from the consumer, the product can then go
through the entire cycle to be a part of the app.
With MMT Labs, we also seek to eliminate the technical handicap and encourage people from non
technical backgrounds to contribute equally to technical innovations on the app. Since most people find it
uncomfortable to develop a complete app feature and an app to go with it. On the labs, you can simply
create a webpage of your “proof of concept” and use the treasure-trove of APIs with us to move to the
app funnel at a certain stage, take a lot of information from the app and make the experience as close to
native as possible with minimal time and effort. This is extremely helpful in getting live user reviews from
our active customer base which is the ultimate litmus test when it comes to the acceptability of any
feature.

So What Exactly Does it Look Like?
The App user section will have an option of MMT Labs, like this

Once you go into the labs, the first thing you see is a pop-up
telling you about the exciting unchartered territory you are
about to enter into.

Next you will find a list of all untested experiments (yes, the
ones which you or one of your friends had created). This is
what it looks like:

On clicking the experiment, you are taken to a page very
similar to what you find on playstore, which gives you a brief
overview of the experiment, representative images and has
user reviews (live user reviews, which will be used later to
judge whether we want to integrate the experiment or not).
You have an option of trying the experience.

Once you choose to try the experience, you are taken to the html page of that experience. You, as a user,
can test the hack in real time & give inputs on the reviews section. Depending on the hack, your
experience might be completely on a webpage or you might be redirected back into the funnel.

Once you come out of the labs tab, you will not be able to see this experience in the real app. Each time
you have to try this experience, you have to go back to labs and voluntarily choose to try it.

How Does It Reduce Work?
In the traditional work flow to make the idea go live, you ideate, you think of all use cases, you code, you
check for user acceptability, you do the QA, you see if it is vulnerable to malicious attacks, you analyze
and reiterate. While this rigorous process is very crucial to development and shipping, every single step
has some friction: bandwidth constraints, fear of not delivering a holistic experience and the worst of all –
upsetting the end user.
With MMT Labs, you ideate, make a prototype and launch it in labs as an html page or a switched off
code, this as you would have guessed by now reduces friction and allows you to try out all types of sane
and insane ideas. Ultimately the product is visible to the tinkering user who has accepted to embrace the
flaws that can occur without the aforementioned steps.
But ultimately you must remember this: With great power comes a great responsibility, i.e. to do your
level best to ship the best possible experience you can, as fast as you can and to let the user decide.
Moreover, MMT Labs uses simple html demonstrations of your ideas. So, anybody with zero experience
in coding and development can potentially bootstrap and create his own idea on the app. Moreover, since
we do not integrate the feature in the native app, nothing done with the experiment has any potential of
crashing/slowing down the app and interfering with our regular business in any way. That is, immense
benefits without any real costs!

Project Specifications
An MMT Labs project needs to be an html experience. While this does make the development process a
lot easier, there are might be some concerns which are addressed below:
● Any html page can be made to be a replica of how our app pages look with minimal effort. We will
be providing with certain basic code snippets to help ease out that process.
● Since we are using an html page, we cannot move to and fro into the funnel with ease since that
will require changing the native app experience. However, we can do the following:
○ Use one of the many APIs available to extract almost any data from the app. The APIs
can be found here.
○ At any stage in the experience, the user can be redirected back into the app using a deep
link. However, once the user enters the app, it will not be possible to bring him back to
the MMT Labs environment
○ In the worst case that we need to hit the funnel multiple times (for example, a new
payment funnel), we can create the intermediary pages on web view for the sake of
demonstration. This process, with the access to all APIs, is pretty doable.
● Lastly, since this will be live on the app for customer scrutiny, any back-end project cannot be
developed. All the projects have to have some kind of interaction with the customer and have to
focus on customer experience in some way or the other.

Examples
We had a tough time getting our heads around this great idea, and hence we thought a few real examples
could help out the reader. In the following lines, we have given a flowchart of how to implement various
projects ranging in scale and functionality through MMT Labs. Most/all of these were final projects from
Trippathon 1.0.

I.

Project Tripbot
The Idea: This hack focusses on using Whatsapp for travel bookings.
● After going to MMT labs menu, choose project tripbot
● Clicking on the project will open a webview with a chat interface
● Chatting with the AI will return top flights and hotels for the required query
● Requesting the complete list/booking will deep link the user back into the app’s native
view

II.

Project SOS
The Idea: This hack aims at creating an on-trip support button
● After going to MMT labs, the user will choose project SOS, this will lead to a native page
asking the user to turn on project SOS (it will also show suitable warnings)
● Enabling project SOS will turn on the part of the Project SOS code in the app,
● Few hours prior to the travel instance (eg. 4 hrs before hotel check-in), a facebook
messenger chat head type of overlay will appear on the user’s device.
● Using the chat head the user can call customer support/ mail them, view booking cards
etc.
Alternative Way
● User can click project SOS on the labs page, which would lead to a web view
● The web-view would have on trip services like View voucher/ call/ mail/ complain/ request
etc.

III.

Project Deadpool [LIVE on Desktop]
The Idea: Compare your flights in terms of the stops, baggage, duration etc. during an
International booking
● Create a webpage on the International flight listing page with an ‘Add to Compare’ button
● The moment the user adds more than 2 flights, a ‘Compare flights’ button gets added at
the bottom of the webpage
● Once clicked, the details of the flights like duration of travel, number of stops, baggage
information are fetched from the Flight listing APIs
● The ‘Go for this flight’ button takes the user to the native flow of Review details within the
App

IV.

Project MonsterMonk
The Idea: One of the ideas which has already been implemented, this aims at creating a street
view for hotels
● Create a web page of how exactly you want the street view to look like
● Use the hotel listing API to generate a listing page of hotels, which would be the first
page of your experiment
● This page directs to the details page of any hotel, which uses the Hotel details API
● From here, the user is directed to your hack of the street view if he chooses to click on it.
● All other options on the hotels details page take him back to the funnel and native
experience.

Bootstrapping Help
Still think it’s too much of a task? Still think you are not well equipped to design your “proof of concept”?
Well, it is not! Bootstrapping and making a live demonstration in html is something which any beginner
can do with some help. In this section, we will provide easy tools which can be used with minimal prior
experience to get the end result.
First of all, you will need a tool to design some basic wireframes and build a webpage to have a final
demonstration of your idea. And this is where the idea of making web pages is really cool, because
opposed to writing native app code, creating web pages is really very easy and does not require coding at
all. Just use one of the following amazing options, and you are set to go:
● Invision
● Omnigraffle
● Bootstrap and its library Bootsnipp
● html5 UP
● Unbounce
● Instapage
● Leadpages
● Strikingly
● Foundation
● Materialize

Okay, if you are still with us and all this stuff about designing and coding does not sound French to you,
we have a number of other useful tools you would definitely want to have a look at.
In case you have no problems in writing a few lines of code, the first thing you would want to look at is our
list of APIs which we have collated so that you could use them in your awesome hacks. You can access
them here.
As for designing, the following frameworks and libraries might come in handy:
● Skeleton
● Neat
● jQuery UI
● Knockout
● AngularJS
● EmberJS
● Meteor
Next up, we have a list of libraries which might be helpful.
● UI Control:
○ Selectize
○ Drop.js
○ Scroll Reveal
○ X-Editable
○ Alertify
○ Unibox





○ Masonry
Charting:
○ Google Charts
○ High Charts
○ CanvasJS
○ ChartistJS
○ Flowcharts
○ AMCharts
○ D3JS
○ Angular Chart
Mapping Libraries:
○ Google Maps API
○ Mapbox
○ Openstreetmap
○ Leaflet
○ Kartograph

Last but not the least, we have a few backend technologies which most likely will not be required for the
scope of Trippathon 2.0. But then, information is never bad:
● Backendless
● Firebase
● Parse

----------------------------------------------------------------------------------------------------------------------------- --------------On an ending note, it is imperative to make sure we all have fun! Let your ideas flow guys. Best of luck!


Related documents


aboutmmtlabs
science 2012 dill 1042 6
study how this great sales1120
landscaping tips which will help1248
cv mikhail tsvik
best options for easy and1512


Related keywords