Work: September

[peeyush-tm]

🔴 - high priority 🔵 - medium priority ⚪️ - low priority ⚫️ - look for some 3rd party 🚀 - Optimise

V2

• [ ] EnY Security compliance

🔴 🔴 V2 -> V3

• [ ] VMS feature list - @veris-neerajdhiman @veris-amoghbanta @veris-st
• [ ] VMS components - @veris-neerajdhiman @veris-amoghbanta
• [ ] VMS versions - @veris-st (eg: offline only, offline + sms, offline + push, onilne etc)

V3

• [ ] V3 Offline First - @veris-ankitpopli
  • ⚫️ Google Firebase
• [ ] V3 Enterprise Ready RnD - @veris-ankitpopli @peeyush-tm (replicated.com)
  • scripts to sync the heartbeat and licenses

Other

• [x] iTech 2017 - @veris-amoghbanta
  • use-cases & pdf for use cases
  • ppt
  • mail
• [ ] payU - @veris-amoghbanta
  • use-cases
    • payU in enterprises as part of V3 payment backend - ekka partnership
    • payU marketplace for personalized applications - noapp
    • payU workplace transformation - ekka customer
  • ppt
  • mail for meeting

🔴 Load Balancing - @veris-neerajdhiman @veris-amoghbanta <-> @veris-ankitpopli

[peeyush-tm]

Updates 6\ Sept\ 2017

1. Mercedes Benz requirements - updates required at both @veris-neerajdhiman @veris-amoghbanta
2. EnY Attendance reporting requirements - updates required at @veris-neerajdhiman
3. Offline Mode Terminal
   1. Android @veris-ankitpopli
   2. Android React Native @veris-ankitpopli @veris-amoghbanta
4. ✅ iTech mail @veris-amoghbanta - 👍
5. V3 -> V2 excel sheet https://docs.google.com/spreadsheets/d/1_T65Bny95AxSy30LV0uRVXfkdutlZDIBnoZR8wAlax0/edit#gid=0
6. Priority V2 requirements & V3 demos

Please add any other discussion point, that I might have missed.

[peeyush-tm]

Updates 7\ Sept\ 2017

1. Mail to everyone (sales + dev)
   • status of the requirements
   • requirements that need a discussion before implementation (EnY, Mercedes)
2. Media files security - better handled via web-server
3. Offline android
4. Offline V3 might be easy
5. React - printing bridge
6. Test https://github.com/grofers/go-codon

[veris-neerajdhiman]

• Media files security - Done (at application level) @peeyush-tm V3 is in initial state so we can secure media files at server level using concept of Xsendfile . For ref https://github.com/johnsensible/django-sendfile

[veris-ankitpopli]

Offline Mode (V3)

Currently app won't show a blank screen when offline :wink:

• [ ] Request Caching
  • [x] The requests fired via re-quests are automatically cached.
  • should provide additional config like caching strategy similar to service workers, for updating stale content (offline first, network first, fastest).
  • [x] service worker on web for offline navigation
• [ ] Offline Template Switching
  • [x] action introduced - $template
  • [ ] document $template
• [ ] Offline App Sessions :+1: :1st_place_medal:
  • [ ] Currently the architecture assumes the session is generated on the backend & it is the sole way of communication.
  • [ ] :thinking:
• [ ] Action Executors - Runtime, WIdget, Template
  • [x] first version hacky implementation - once the application has been loaded different executors can receive actions & perform actions offline.
  • [ ] Runtime to manage offline network retries for in app requests using redux-offline
• [ ] Action Queues
  • [x] first version already implemented - credits to @veris-abhinavanand
  • [x] persistence - switch out custom middleware which manages syncing with database in favor of community managed store enhancer like redux-persist
  • [ ] retry actions :thinking:
• [ ] App specific DB
  • [x] Each app gets its own store.
  • [ ] The store can then be exposed using jexl or st for complete offline query language & own database access.
  • [x] move action queues to app specific db