[Feature] [Implementation] Alternative to Nestled Vaults to Save on RAM resources

Platform

[ X] iOS
[ x] Android

Obsidian Mobile version: v0.15.6


Hi all,

I have been testing on iPad only yet, so I semi-ticked for Android for possible future use on that platform and of course the same question can be asked by Android users as well.

Issue:
I have a vault of 15000 items sorted into A-Z subfolders (it’s a mini-lexicon basically) and a main assets folder to link to individual entries having images.
My workflow necessitates having (at least/only) two apps in the foreground, Obsidian being one of them, but while I am out of Obsidian for a little while, the app just doesn’t seem to be able to stay available and needs to be restarted. A leaner vault with other projects doesn’t do that.

Workaround:

  1. Use an MD Editor to access my folders/files and edit them outside of Obsidian. This is not what I want to do, as i cannot edit backlinks and I cannot work with images during my workflow. And generally I like to learn or automate my finger movements for my workflow, otherwise I break my (brain) flow/zone.
  2. Trying to access only a portion of the vault to save on resources used by iOS and not have Obsidian exit on me.
    This is what I’m trying to work out but at this point I cannot think of anything else but a way to access subfolders (A, B, C, etc.) as subvaults, which I believe would involve nestled vaults (at this point I don’t even care about graphs or anything else, although the need for a right approach must be thought out thoroughly to forego future issues and the only way to test large amounts of data is to use your own precious data you accumulated for years and years).

I am on an iPad mini 4 running iOS 15.5 and have not been happy with it. My service guy installed it without consulting me and I tend to think that my iPad is not working to the best of its ability, so I don’t even know that other people are having similar struggles or not (mainly to to with iOS versions or anything else).
It is possible that my Obsidian struggles are aggravated by personal/technical (hardware/software) issues. I do not know…

I want to do my main work on the light iPad and not on PC, so this is top priority for me.

Question:
Does anyone have an idea how to offload on a heavy main vault while retaining vault-specific functionality that would not involve creating nestling vaults (as it can be risky)? (In the meantime, I’d still have to try it, of course, after making some backups.)

I was looking around on the forums (elsewhere too) and saw ideas for Focus and Workspaces as alternatives to nested vaults and I don’t know any updates on those ideas or how exactly they could help with my case. I want full functionality and less resource dependency. Please don’t anybody tell me I can’t have my cake and eat it.

Anybody using maybe a plugin that helps with my case?
Anybody using a working workaround I might be interested in?

Cheers

In the end, I’ve found a straightforward method.
I am writing it up for the benefit of others.
(You see many times you’ll come up with a solution for yourself but writing about the problem and the pressure that you laid yourself bare that is showed your stupidity and lack of imagination online for all to see will make you work harder; external pressure for a lot of people is greater than internal.)

Create a dummy vault which you can call Prep- something, or anything.
I was thinking of creating a shortcut that uses Obsidian URI to fetch (copy) the file specified (to be inputted) in a pop-up, but since sometimes I don’t recall the actual name of the note and would need to look it up, why would I not set up the Files app in two panes and drag and drop from one folder (vault) to the other (this results in a move) while I’m at it? When I’m done editing, I move the note back to the original place with the same drag and drop. No need to remember to sync files back later either.
In case I’d need to do that, I use FreeFileSync (which I use to transfer everything to Android as well).

I am not quite pleased with this workaround but it will have to do for now as I already spent nearly two weeks porting my research to the new environment (PanDoc did not work out for me) and need to go back to being productive.

Thanks for reading

Cheers