The size is primarily due to Electron, Nimble&#x27;s backbone. Unfortunately, a large portion of Nimble&#x27;s size is due to to Electron, and there&#x27;s not a whole lot we can do about that aside from shifting the project to a completely different framework, rebuilding Nimble from the ground up. Although this is true, we&#x27;re still doing everything we can to bring the size down.<p>The information provided by Wolfram&#x27;s API is rather limiting, and definitely not as extensive as the information provided through its web service. We&#x27;ll see what we can do about this problem.