Mission: Startup Battlefield: SF: 2017

[peeyush-tm]

Event Schedule

WIN WIN WIN 🥇

GET READY

Month	Winning Strategy
FEB	⬇️ ⬇️ Admin Panel + Logbook (basic)
MAR	IAM (full) + Extend Micro Services + Rules Engine + Logbook (+all use cases)
APR	VMS (full)
MAY	Microservices (swagger, non-swagger) REST interface
JUN	SUBMIT APPLICATION
JUL	Make it PRETTY
AUG	Make it AWESOME
SEP	Demo Steps 1. register a new user (user: A) => login => no apps 2. login user (user: B) => show him his apps (wow!) 3. login admin => show VRT, widget, services, processes, members 4. admin => create a new widget => new VRT => ship to the member (user:B) 5. user:B => gets a new app (wow!) 6. user:A => search organization and becomes a member => admin ships a new VRT to member (user: A) 7. user: A => receives the new VRT (much WOW!)
SEP	WIN WIN WIN

Scaling

Inspiraton - Firebase - https://hackernoon.com/how-to-build-a-product-loved-by-millions-and-get-acquired-by-google-the-firebase-story-82dab4e3e80c#.u6wkq1snm

Less Inspiring, but useful - https://levels.io/build-a-community-around-your-startup/

Mar - Apr

• Build Product
• Define easy standards for effortless usage and UX
• Admin Panel

May - Jun

• Build tutorial series - period: 8 to 10 weeks
• Start with Test Suite
• Start with building the Tutorial
• Admin Panel & More Automation
• Launch RE-Org on github to support React ecosystem
• Add more open source libs to Re-Org

July - August

• Start attending Meetups
• Gather developers/ users/ hackers
• Prettify, beautify, UXify the Admin Panel
• Internal Reporting tool for checking the user activity
• Add more open source libs to Re-Org

September - Go To Market

• Hackathons
• Battlefield

Work Breakdown:

March

March Week 2 ( 6th -10th )

• Make the static admin panel usable.
• Refactor & cleanup back end code. Introspect, & Inspect code.
• Revisit Process/Widget Schema generation.

March Week 3 ( 13th -17th )

• Email Service
• SMS Service
• Keen Service
• Nested Process creation - on activity log failure, send admin a mail
• Widgetize Admin Panel ( More components in registry, more actions in registry )

March Week 4 ( 20th - 24th )

• Revisit Authentication
• Veris Runtime Types (User/Terminal)
• Revisit Membership - Membership type - Update clients with tweaks according to membership type.
• Widgetize Admin Panel ( More components in registry, more actions in registry )

March Week 5 ( 27th - 31st )

• Rule Engine for Widgets only - Add member if user emails ends with @veris.in (Moved to last, coz we need a strong base for rules & less moving parts)
• Test Suites for LogBook
• Finishing Touches

April

April Week 1 ( 3rd - 7th )

• Introspect. Inspection & code clean up.
• V2 Week

April Week 2 ( 10th - 14th )

• Invites Service
• Push Notification Service
• Widgetize Admin Panel ( More components in registry, more actions in registry )

April Week 3 ( 17th - 21th )

• Rules Engine for Runtimes - Either/Or Widgets

April Week 4 ( 24th - 28th )

May

May Week 1 ( 1st - 5th )

• Introspect. Inspection & code clean up.
• V2 Week

May Week 2 ( 8th - 12th )

• RnD on REST Interface and other Protocols which we can integrate in V3

[peeyush-tm]

Battlefield Story: Connected workplace - the world is your workplace.

Problem

• Incumbents have a focus on hardware & have a closed ecosystem
• Independent software vendors are not able to comply with the security standards of the enterprise
  compromised apps are being built, that instead of making the workplace more productive are, in fact, degrading the workplace productivity.

[peeyush-tm]

Future Work

• Physical Web
• BLE, Geolocation based apps
• IPFS - peer to peer web
• Offline Apps
  • push/ event based arch
  • data management
  • workflow execution locally
  • templates avaliable locally
• AI/ ML Strategy
  • uniform UX
  • auto deduction of the best way to show the template to the user, on the basis of the client interface
  • smart apps, that saves user a lot of time

[peeyush-tm]

Note to self Entertain users while they wait - transparent apps that tells the user

• average time it takes to complete the step
• what is the next steps
• when is the next step going to happen

things like this would reduce the user's frustraiton. we are building a platform where in user should be able to use the services - instantly - on a click of a button .