Work: May \ June \ July 2017

[peeyush-tm]

Continued from #50 #45

• V2: As discussed in the meeting for EnY

  • 1st Week of May - Bulk Upload
    • add members
    • delete members
    • update members
  • 1st Week of May - Assign Venue Admins
  • End Of May - Daily Reports should have all the visitor data
    • Forms Data
    • Visitor Data
    • Least Priority - Visitor Picture

• V3: Documentation & Start wrapping up the work for @veris-abhinavanand => transfer ownership to @veris-amoghbanta

• V3: Microservice List - @veris-neerajdhiman @veris-ankitpopli

  • Weekly: MAR \ APR \ 2017 #50 - Cotinued from March/ April

• V3: Testing @veris-neerajdhiman @veris-ankitpopli @veris-amoghbanta

  • Unit
  • Integration

• V3: Admin Widgets Continued from Weekly: MAR \ APR \ 2017 #50 - @veris-amoghbanta

• V3: VMS, Logbook Continued from Weekly: MAR \ APR \ 2017 #50 and Apps from TODO: Apps #54 - @veris-neerajdhiman @veris-ankitpopli @veris-amoghbanta

• V3: Global Instant Apps - ios - android - web (PWA) @veris-neerajdhiman @veris-ankitpopli @veris-amoghbanta

• V3: Test Automation - backend, clients - ios, android, web @veris-neerajdhiman @veris-ankitpopli @veris-amoghbanta

• V3: Reference FEB Work Work: FEB 2017 #38 March/ April Work: MAR\ APR 2017 #45

• V3: List Open Source Items and gather them together TODO: Widget, Component and Template #51 TODO: Process, Microservices and 3rd Party Client SDK #52 TODO: Talks, Hackathons, Open Source #53 TODO: Apps #54

Discussion Update - 3\ May\ 2017

• @veris-abhinavanand

  • KT to @veris-amoghbanta
  • Start with open sourcing the components
  • Start with the documentation for the components - per component wiki
  • Start with the documentation - "how to build a component" and working in V3 Wiki
  • Actions to call the other components would be rendered in Modal Box, instead of "intent based"
  • After KT, Documentation, Unit Tests - continue to work on PWA component integration

• RnD: Android Instant app to launch V3-Instant-App

• @veris-neerajdhiman @veris-ankitpopli - store the configuration of each worker node (widget, runtime, process) as in, out, mapped in, mapped out

  • output and input, for each node (step) are known to the admin
  • 
  • python lib modeled after yahoo pipes - https://github.com/nerevu/riko

• @veris-neerajdhiman @veris-ankitpopli - Template is a service

• @veris-neerajdhiman @veris-ankitpopli @veris-amoghbanta - release !

Discussion Update - 4\ May\ 2017

Enough Said

Highlights

1. Feedback to the user using the - App / Widget (this app will self-destruct in t-30 seconds)

   • we can show the user - what's going on in the backend
   • we can show the user - what is the expected time to complete
   • we can show the user - how long before he can consider this as failed
   • love thy user!

2. microservices will hide their logic and data, would only open their API and documentation

3. System workflows - hidden from the admins, useful in common cases as

   • policy assignment
   • onboarding

4. Onboarding

   1. selfie
   2. Profile Details
   3. Preview & send OTP
   4. verify OTP & next
   5. Show profile & organizations => never force the user
   6. show the apps to use => default apps
   7. 

5. Component Action API

   1. human readable
   2. on typing <=> when a user starts typing
   3. communicate with backend to fetch user data <=> HTTP request to process
   4. when user stops typing for 30 seconds, communicate with backend to fetch user data <=> HTTP request to process after 30 seconds

6. Rules

   1. human readable
   2. Chaining
   3. parallel or serial

7. Defaults Apps TODO: Apps #54

   • IOT App (mother fucking IBM - https://yourstory.com/2015/03/internet-of-things-application/ )
   • 

• Next Demo - 15th May - 🤓😎
• Final Demo - 19th May - Friday - 👩👩

Discussion Update - 5\ May\ 2017

What do we value - Awesomen (of course)

There are a lot of things that can be awesome, what awesomeness do we value?

• something innovative/ new/ fresh (eg: reusable rockets, arovia.io)
• something funny/ fun (eg: asciimap, agentM)
• something challenging/ some solution to a problem (eg: somg towers, the boring company)
  In general, we like a fresh and new approach to a solution or an idea.

What do we don't like?

• copy/ paste/ repeat

So to achieve the awesomeness we praise to being awesome, we need to get to the edge and then one more step to go over the edge.

Awesomeness needs Expertise needs Focus

Solving a problem is more about finding an interesting/ challenging/ hard problem (finding an easy problem to solve is not why we are working here day and night)
Finding hard problems needs the expertise to know that it's a problem and "this is a bug, not a feature"

The conclusion of the whole story - Focus.
Based on your own interests, I am putting more responsibilities on your heads.
@veris-neerajdhiman - (DevOps + Monitoring + Management) of the Microservices
@veris-ankitpopli - (Middleware + Integration + Orchestration) of the Microservices
@veris-amoghbanta - Micro Apps + Runtime Management

These are your primary responsibilities (you would have to do more and be more), your decisions would matter here.

Think carefully, this is a huge responsibility.

• you need to evaluate all possible tools for the job
• you need to evaluate pros and cons of all the approaches you would follow
• you need to keep in loop all the people in the team about any decisions
• you would need to evaluate your own requirements and build the best-suited solution
• you would need to keep on innovating and improving the product part lying in your domain

[peeyush-tm]

Discussion Update - 15\ May\ 2017

• 2 Weeks => 2 Releases => 1 Release per week

System Processes - @veris-ankitpopli

• CRUD
  • Organizations
  • Members
  • Processes
  • Widgets
  • Applications
• Onboard
• Self Profile

Simple Onboarding & Admin Panel - @veris-ankitpopli @veris-amoghbanta

• Simple Onboarding
  • ask for
    • email
    • password
    • sign in
  • Landing Page
    • Welcome Message
    • tutorial & other links (later on replaced by eagle eye dashboard)
• Menu Items post-onboarding
  • for both
    • new user
    • existing user
  • organizations
    • page sections
      • Owner of List
        • Actions => manage members | manage organization
      • Member of List
        • Actions => view organization & membership details
  • members
    • members list columns
      • member name
      • organization
      • invited on
      • joined on
      • Actions => manage membership
  • processes and services
    • page sections
      • Processes list
        • list columns
          • name
          • created at
          • published at
          • Actions => manage processes
      • Services list
        • list columns
          • name
          • created at
          • published at
          • Actions => manage service
  • components and widgets
    • list columns
      • name
      • created at
      • published at
      • Actions => manage widget
  • applications
    • list columns
      • name
      • created at
      • published at
      • Actions => manage application
  • application log
    • list columns
      • organization
      • application
      • user
      • started using
      • ended using
      • Actions => more details

Kubernetes + Docker + Web Service Monitoring - @veris-neerajdhiman

• Application Perf Mon - newrelic
• API Monitoring - https://github.com/cachethq/Cachet
• Kubernetes monitors the Docker so that's done
• App Analytics - https://count.ly/ - https://github.com/countly/countly-server

[peeyush-tm]

Discussion update - 27 \ May \ 2017 - Roadmap (Images): Application Development platform for Companies to instantly deliver applications on user's preferred interface #1

[peeyush-tm]

July Work

Discussion Updates: 5th June 2017: Demo ready for YC & First Product Release (closed alpha release)

Onboarding

1. Login/ Register
   1. • Open the link
   2. • Put in email and password
   3. • Login / Register
2. Landing Page
   1. - Show Tabs
      1. - Profile (With a status of profile completion)
         1. - In profile, there would be list of information, QR, image
         2. - a button to launch admin
            1. - admin panel would require Phone number validation - OTP (MFA seems like a good option for admin)
         3. 
      2. - Apps (all the applications)
         1. - Instagram - Organization chooser
         2. 
      3. - Default Apps
         1. - Badge
         2. - I wish for an app that can ......... for me

Onboarding Use Cases

1. - The person knows the direct link to our online hosted site
   1. Normal onboarding process and landing to Apps page
2. - The person has been invited
   1. - is a new user
      1. land on the APP PAGE
      2. on clicking the GET STARTED
         1. Onboard the user - email and password
         2. Use the App
         3. Rate the app and complement to the creator
         4. Send mail to both the creator and user, about the complement given
   2. - is an existing user
      1. land on the APP PAGE
      2. on clicking the GET STARTED
         1. Use the App
         2. Rate the app and complement to the creator
         3. Send mail to both the creator and user, about the complement given
   3. - is an existing user, but first-time app user
      1. land on the APP PAGE
      2. on clicking the GET STARTED
         1. Use the App
3. - Invitation was sent via
   1. email
      1. email template should display the app preview
   2. SMS
      1. 140 perfect characters
         Meghna has created a personal app for you, please share your app experience at - link
   3. Social Media
      1. 140 characters
      2. image preview of the app

Design

1. Clean
2. Minimal
3. Follow the Airbnb lead
4. Follow the lead of - https://dribbble.com/shots/3440657--3-Invisible-series-TO-DO-app
5. Follow the lead - https://dribbble.com/shots/3431464-Music-lover-app-concept
6. Admin Panel would be the INVERT OF normal APP
7. https://dribbble.com/shots/3543964-Mixpanel-Styleguide

Closing The Loop

1. - Build an app
2. - Ship and app
3. - Check the app usage
4. - Love the feedback

What would be our WOW moment - Receive the Feedback on the App

Uniform (zen) Experience

Positive messages throughout the app

June Timelines till Demo

Date	Work
5 June	Session management and default widgets - session & feedback
5 June	Setup admin panel with the desired onboarding flow
6 June	integration of the new admin panel and onboard process and session management
7 -8 - 9 June	Design and finishing

[peeyush-tm]

Congratulations for graduating from YC Fellowship 🎉

Discussion Updates 17 June 2017

Next => #42 Mission: Startup Battlefield: SF: 2017

Timelines: 3 Weeks

• New Interfaces - Voice and Bots @veris-neerajdhiman @veris-amoghbanta
  • https://github.com/hackerkid/bots
  • Tech: Bot: Veris Bot for Frontdesk random-ideas#8 - Tech: Bot: Veris Bot for Frontdesk
  • React Voice (React could be the new JS :) )
  • React Bot (React could be the new JS :) )
• MVP: Conference Room Manager @veris-ankitpopli
  • Create an email and make him a resource in the mail & calendar provider (gmail etc)
  • The newly created email needs to be mapped with the Terminal (conference room)
  • Create an invite for the Conference Room
  • Let people check the Conference Room booking status on the Terminal
  • Let people check-in and attend the meeting
• Code cleanup
  • open all the libs
  • code documentation and hosting
  • bringing the code under one umbrella
  • reamove unnecessary code
  • unit testing
• integration testing & devops
• Wiki / Documentation updates

[peeyush-tm]

Discussion Updates 20 June 2017

• There is no USER there is only APP
  Sessions are now - APP Sessions
• New module - workflow session
  to manage the per use data
• APP/VRT <=> BOT
• App Store App/ASA <=> Messaging Platform/ Voice Platform
• Templates are there to => Send Data and Receive Data
  • Bot Template
  • App Template
    can be mapped to work with each other

[peeyush-tm]

Discussion Updates 5 July 2017: What Next?

• Lambda / MBaaS / Graph QL
• Event-Based Architecture
• GAIM service integration (cloud foundry)
• Firebase like Go To Market (Free stuff, best programmers, community, content, tutorials, marketing)
• Better App Builder + Better Admin panel
• Release stable 0.0.1
  • unit test
  • integration test
  • scalability tests
• More apps TODO: Apps #54 + Existing Apps
• App analytics
  • app performance
  • app performance trace
  • micro service performance tools
• More ecosystem connectors
  • DB
  • salesforce
  • SAP
• More Interfaces
  • Voice
  • Bot
  • VR/AR
  • ios/ android/ web
  • FB/ Twitter/ GH
• AI/ ML/ Data - what data is useful to use?
• Prepare a questionnare
  • how frustrated are you with app updates?
  • do you know FB is taking 160MB space on your phone?
  • Do you think mobile development is a challenge?
  • questions related to the frustration of the user/ IT Admin/ Developers
• Extend microservices & backend
  • gRPC
  • DB clients
• Social integration with user profile
  • FB
  • Linked In
  • Twitter

Inputs from the team

• Admin Panel
  • Steps/ Screens
  • Drag/ Drop
  • Easy app building
• App Side Car/ Plugin driven apps
  • change the default functionality of the app
  • understand the user behavior and expectations
  • let the user choose how he wants his apps to be, what all plugins he would want to enable in his apps

[peeyush-tm]

Discussion Updates 5 July 2017: What All?

• [mvp] build an app that can run on multiple platforms/ interfaces
• [mvp] connect the app to data processing unit - backend - backend is the brain. Backend decides for the information to be displayed, information to ask the user
• [mvp] show the app usage, by the users, to the admin
• [note] fast data exchange matters - fast is addictive - fast is instant
• [next] making the backend data integrations easy
  • Generic API integration
  • REST API support for swagger, blueprint, etc
  • gRPC
• Extend and abstract the client interaction middleware, to support any number of interfaces
  • Voice
  • Bot
  • VR/AR
  • ios/ android/ web
  • FB/ Twitter/ GH
• App analytics
  • app performance
  • app performance per interface
  • microservice peroformance
  • user experience
• A/B testing & UX analytics for the apps
• Workflow analytics for the backend
  • the time it takes to complete the full workflow
  • the time it takes per process in the workflow
  • full interaction logs per session
• Faster clients/ interfaces
  • taking things local on mobile / desktop
• Easier to build apps
• Data visualisation components & report components
  • DIY viz
  • DIY reports
  • DIY dashbaord
  • analytics functions
• Monitoring for all the API and services
• Extend backend support for more platforms and protocols
  • graphql
  • MBaaS
  • Protobuf/ gRPC
  • DB
• Event driven backend and data processing
• Event driver data exchange between frontent and backend
• Offline first apps - couch db type system
• Hybrid deployment of the platform and the services
  • hybrid apps - SDK
  • on premise deployment
• Replace the backend with GAIM services/ serverless/ lambda
  • Auth(n)
  • Auth(o)
  • API G/W
  • Datastore
  • MQ
  • Cache
  • Step Function
• App simulation over multiple interfaces - simulate apps before deploying
• define Standards for app creation
• developer portal and app store
  • components
  • app building
• Designer portal/ plugins
  • sketch
  • photoshop
• Consumer portals
  • manage apps
  • manage app data
• Interact with the apps local to the mobile (eg: fitbit) instead of calling the fitbit backend
  • run workflows locally
  • interact and excahnge data with other native apps locally
• Smart apps & smart workflows
  • suggest app to the users
  • suggest app to the IT admin
  • suggest improvements to the workflow
  • dont ask user the redundant information, that can be derived from somewhere
• interface switching for the apps session (from iphone => google => alexa => desktop => web). the session should continue
• VPN enabled apps
• Domain specific language for the platform/ Expression language => JSON

[peeyush-tm]

Discussion Updates 5 July 2017: Free Stuff/ Open Source?

• [open] SQL like language to connect REST APIs
• [open] Phone Gap like framework for React / Native
• [free] basic apps that doesnt need to interchange data woth the backend
• [free] basic apps with basic one step web service interaction, with basic form components
• [open] widget/ component SDK
• [open] Kong analytics for API
• [open] Microservice performance monitoring tools
• Viral Apps - smart bahu ?? remember?
• [open] Application integration SDK like Stripe, where in a developer can use the a single SDK to integrate any number of backend services by ny number of service providers

[peeyush-tm]

Discussion Updates 5 July 2017: MVP/ Data?

• [mvp] Build app -> Ship App -> Deliver App instantly
• [mvp] gather the data from the app -> show it to the admin
• [mvp] gather the feedback from the user
• [next] build apps that can do more => complex workflows and rule engine
• [next] infinite services integrated on the platform
• [next] infinite protocols supported on the platform
• note ship this platform in the filed => listen to the customer and user => improve

Data That matters

• Organization
  • user analytics
    • UX
    • more services the might be of user's interest
    • redundant information in the workflow that can be removed
    • better way to build the app
  • app analytics
    • app loading time
    • user session
    • time taken to render components
    • user's comfort in filling the data
    • data interchange latency, miscroservice performance
    • google analytics for all the apps
  • micro-service analytics
    • service latency
    • service performance
    • time take per-session
    • request analytics
    • response analytics
    • workflow improvement suggestions
• App - micro app
  • does one job well
  • runs on all the interfaces
  • uniform UX to the user

Data That matters to us

• User Experience
  • rendering time for
    • component
    • widget
    • application
  • App loading time
  • data excahnge duration, exchange latency
  • user behaviour
  • more apps for the user
  • workflow execution time and the steps in the app
  • types of apps for the user
  • types of services for the user

[peeyush-tm]

Discussion Updates 6 July 2017: Onboarding?

Onboarding is the most important part of the application, the user should be guided on to the action he should perform - this is an app platform, we should offer the app to the user directly.

Next the user would be interested in searching more apps, we should take him to the marketplace panel.

A few users would be interested in building the apps, we should provide user a way to access the admin panel and there in have a pre-built unique app for the user to try and ship to his firends and social network,

What do we want to achieve - use app -> add app -> build apps -> ship apps -> receive feedback.

[peeyush-tm]

Discussion Updates 7 July 2017: Free Stuff?

• Expo viewer - Free
• IPFS - peer to peer internet 👍
• React Voice 👍

[peeyush-tm]

Discussion Updates 20 July 2017: July Closing.

• [RnD]: mesh of application's actions, cross calling, personalisation and modular apps - smart apps, auto-personalisation
• EnY Use cases: https://drive.google.com/drive/u/1/folders/0B14j7MOVHpQGaVJYTlpKYlpKMms
• Push Notifications
• Launch App from Email & Email templates
• Portal for organization admin to check his app usage. This portal is not NoApp, this is Ekka Portal. Ekka admin portal is sort of subset of NoApp and has fixed functionalities
  Ekka Portal
  • apps
    • VMS
    • Logbook
    • ...
    • Attandence/ Geo Tracking/ BLE
  • members
  • member app usage data
  • app usage data
  • reports & dashboard
    As you can see this is a subset (not hard subset) of NoApp platform

[veris-amoghbanta]

Discussion/Idea, 27 July 2017

Some way to allow admin to send the app to a couple of people to test, before releasing it on our marketplace and automate this whole process.
For us it should be no extra effort, just a workflow which creates a group of testers and admin can assign app to that group and if all testers are happy, release the app.

Microsoft is trying to cater analytics, dev-ops and testing of android and iOS apps on a single platform. We can also do some of this stuff. This is the link to the talk.