@priyanshu

I have finally finished V1 for Rchive. GH action is running to release apk rn.
and if that finish (this is third try) i feel it will this time.
than I am good to go i have tested all so far and I tried to make UI the best I can.
App Size it little big as I am using custom fonts may be in future i will fix it too.

I have rewrote the UI and removed that extra fs thing instead now all in one db

As per the review I have added a DEMO video on landing page. Also now it is easy to setup the project also
you can test with this example if you want
https://github.com/P8labs/trackion-js/tree/master/examples/full-website
Now it will be easy to review

Today I am able to make it work I have removed separate database from vault and added a syncing logic when vault is opened a sync fn is ran that registers all the entries of the vault also fixed treeURI and location as there is some android restrictions. Also fixed alot of bugs
now, we can create notes easily backend part is almost done only presentation is remaining.

I have migrating this project from #macondo to #stardance.
My devlogs for this much of time is recorded here
https://macondo.hackclub.com/projects/5481

AND the project is not shipped so there is no reward I get from that event.
Please don’t feel it as a inflated recorded time. I did put effort and logs everything i can.

I have implemented a separate package for SAF android storage access it will just help a lot

Finally I have added AppState currently solved that default vault implementation but I will change it again in currrent version isDefault is the field of vault registry but it makes it dependent on vault feature so i will be changing it will remove this from vault entry and keep it into app config database

I have implemented two separate db one for app database and other is for vault level db in which only vault related things will store

i think i need redesign currently I have mixed alot mixing sharedprefs, drift db, onboarding and vault management.

Now, I am going to fix and rewrite my logic now is to remove shared prefs and have a app database that will be private if app deletes it will be deleted. The flow will be when user opens app it will load data from this main appdatabase all vaults and its data this database will store only app data like logs, config, vault data and default vault
if no vault opened user can open existing or create new that will register it into appdatabase than when the vault opens will create a separate vault database that will have all data related to vault only that can be synced.

as i am following MVVM clean architecture:
We will have features as follows
for now simple comman - AppDatabase

• Vault, - this is a separate feature
• Notes, - it is separate thing

New note auto markdown view added with custom package and patches.

I am working on authentication and learning clean architecture MVVM

I have setup flutter initial project will start implementing the core things.