labn36 / cashbook Goto Github PK

use aws certificate or cerbot whichever as lower ssl handshake.
setup ci/cd on this in future.
for now
launch EC2
install nodejs
install redis
install pm2
install nginx
convert lambda functions to a repository
test it on http
setup ssl using certbot

so far as a POC data sync is implemented using sqlite on both client and server side.

this means on both side we'd have to use sql. this is fine for now but in future I'll add support for nosql(personally i like it).

also in future i'll try to make existing data sync more resilient but for now it's fine. it can work well with basic apps.

currently having access related problem on minio on separate(for now workaround is to use another location bloc for each bucket)

In this app i want to mainly implement phone number and email based login. for now we'll only implement phone number based authentication.

when we talk phone authentication Firebase seems to be good option and infact i even tried that but it takes quite a long time than it should(on an average you'll see message coming in 4-5 seconds) but in real life for production app this time is a lot. through a simple aws sms service(along with lambda and elasticache) i was able to achieve this under 3-4 seconds which is perfectly fine to me.

one more problem with firebase is that you can't change the actual text message you want to send so you'll have to stick with the generic message.

even though aws now supports flutter but it does not yet provide a proper implementation that the reason i had to implement my own auth flow.

Current Implementation: as of now very basic auth part is done.

what's Left:

1. saving jwt into shared preference
2. linking user profile with aws cognito, although i will work without it but this is recommended way for good architecture flow
3. implemeting OTP invalidate flow after certail expiry passed
4. implementing Resend OTP flow
5. a good looking UI with ability to handle all use cases(right now it just works but not up to the mark)
6. rate limit and abuse restriction

Once this all is done, I'll try to see how feasible it's to implement email based login(passwordless or gmail)

Note: for now I'm not planning to support IOS as it's out of scope of this project untill we finish the android MVP

support multi language support

to sync data to cloud we'd have to sync the database to the server.
there are couple of places you can call(on app restart, on app resume, network changes) but it should be rock solid and make sure it doesn't call multiple times.

websocket/socket implementation for customer chat or real time data sync or any other event based action

allow user to set the pin on the app and also implement how to reset the pin