using react native in a digital health solution
TRANSCRIPT
React-NativeArchitectureconsiderations
16-08-2016Vincent Laulagnet
2
About myself
• Project manager in High tech for 10 + year
• micromove.com founder
• Offers Complete Digital platform for clinical researches
• Consultancy services:• Project Management• SW architect & Full stack developer • Technology scouting
3
Content
1. Digital Health Platform overview and key requirements
2. React native application architecture
3. Highlight in some components aspects- Realm Database- Redux structure- Protocol stack: introducing WAMP- JWT usage
1. Micromove.com Digital Health platform
5Our mission: providing new insights for improving the patient health
Patient
Medical information
Monitoring
Cost management
New treatments
Behavioral changes
Diagnostic
6
An end to end secure and validated solution for research purpose
ContinuousGlucose meters
Patient app +Activity tracker
Patient app
Secure Link Data Management
Operations support
Analytics
Smart insulin pens
7
High quality data as an output
8
Key requirements for the mobile application
1. Modular and easily extensible.
2. Based on Open Standards
3. Secure and compliant
4. Rapid development
5. Android support and cross platform
2. Mobile application architecture
10
Mobile application architecture
Realm DB
UIComponent 1
UIComponent 2
UIComponent …
Redux StoreActions Reducers
Navigator
Network Drivers
Device Drivers
User Interaction
3. Highlights in some applications aspects
12
Realm DB for the client DB
1. Integrated in React Native and the native Android/ iOS parts
2. Type safety
3. Good performance
4. Enable advanced query
5. Encryption option
!Remote DB synchronization mechanism needed
13
Redux
1. Keep your application organized
2. Good scalability
3. Easy to use
! Different options to handle asynchronous events
14
Web Application Message protocol
Web Socket
TLS
WAMP
Open protocol with good performance and functionalities
• Functionality- Publish/Subscribe pattern- Topic selection and validation- Remote Procedure Call
• Secure through TLS.
• Small overhead on top of web socket
15
JSON Web Token
• Open Standard
• Strong security with 256 bit encoding
• Great flexibility to pass different parameters.
