This is a very common practice in mobile development. Read up on it
[CLOSED] Test user credentials in Appwrite
Votes
1
Replies
24
Participants
Unknown
Messages
25
Rank 3: Container
this is not fully secure , there is way to reverse this process
What's this process?
Rank 3: Container
shrinking code
I'm askign what's the process to reverse?
Rank 3: Container
i dont know , but reverse engineer can do it
Shubham it seems like you're trying to acheive the impossible.
Rank 3: Container
i think this is better approach
Hacking is always a possibility
An app or website is never 100% secure
It's just harder to get into
Rank 3: Container
i know , no body can fully. secure application
Exactly.
So you shouldn't be looking to do this - make hacking impossible
Rank 3: Container
but its my work to atleast check all , that i can think its easy
It is easy, but it looks like you want 100% security. This is virtually impossible 😅
Rank 3: Container
yes but we can make the layer so that normal hacker can not do this
The mthod I suggested, of sending the mobile number and and otp on cloud function is as good as it can get
At least for now.
Rank 3: Container
i know it , even big platform like udemy and courseera app data leak
Rank 3: Container
yes this is better approach
Rank 3: Container
Actually i have planned to move completely from firebase and django to appwrite
Rank 3: Container
so in migrating , i have lots of problem , and i have to ask every question
that's absolutely okay
[CLOSED] Test user credentials in Appwrite