Open peeyush-tm opened 7 years ago
System Processes - @veris-ankitpopli
Simple Onboarding & Admin Panel - @veris-ankitpopli @veris-amoghbanta
Kubernetes + Docker + Web Service Monitoring - @veris-neerajdhiman
Discussion update - 27 \ May \ 2017 - Roadmap (Images): Application Development platform for Companies to instantly deliver applications on user's preferred interface #1
Onboarding
Onboarding Use Cases
Meghna has created a personal app for you, please share your app experience at - link
Design
Closing The Loop
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 |
USER
there is only APP
Sessions are now - APP Sessions
workflow session
to manage the per use dataOnboarding 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.
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.
Continued from #50 #45
V2: As discussed in the meeting for EnY
V3: Documentation & Start wrapping up the work for @veris-abhinavanand => transfer ownership to @veris-amoghbanta
V3: Microservice List - @veris-neerajdhiman @veris-ankitpopli
V3: Testing @veris-neerajdhiman @veris-ankitpopli @veris-amoghbanta
V3: Admin Widgets Continued from #50 - @veris-amoghbanta
V3: VMS, Logbook Continued from #50 and Apps from #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 #38 March/ April #45
V3: List Open Source Items and gather them together #51 #52 #53 #54
Discussion Update - 3\ May\ 2017
@veris-abhinavanand
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
@veris-neerajdhiman @veris-ankitpopli - Template is a service
@veris-neerajdhiman @veris-ankitpopli @veris-amoghbanta - release !
Discussion Update - 4\ May\ 2017
Enough Said
Highlights
Feedback to the user using the - App / Widget (this app will self-destruct in t-30 seconds)
microservices will hide their logic and data, would only open their API and documentation
System workflows - hidden from the admins, useful in common cases as
Onboarding
Component Action API
Rules
Defaults Apps #54
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?
What do we don't like?
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.