As I can see, we use some markers for FlowCrypt drafts. I mean flowcrypt:link:draft_compose:
On Android, it produces additional actions and makes code less readable and some approach oriented.
The problem is that Android covers more cases than the web app. The web app just covers encrypted drafts for Gmail and that's all. But Android should cover regular and encrypted drafts for Gmail as the first step, and regular and encrypted drafts for other providers as the second step.
Could we reject any additional text from a draft and leave just the original text?
Yes, you don't have to replicate these draft id tags on Android. You can do without, and later we will figure out how to update browser extension to work nicely together.
As I can see, we use some markers for FlowCrypt drafts. I mean
flowcrypt:link:draft_compose:
On Android, it produces additional actions and makes code less readable and some approach oriented.The problem is that Android covers more cases than the web app. The web app just covers encrypted drafts for Gmail and that's all. But Android should cover regular and encrypted drafts for Gmail as the first step, and regular and encrypted drafts for other providers as the second step.
Could we reject any additional text from a draft and leave just the original text?
I mean instead of have the following text
have just the next one
I understand that you need to have
draftId
somewhere but maybe we can store it in another place or fetch it dynamically.