No, though I used to think this as well. The way your data is organized has a profound effect on the shape of the software that manipulates it. Imagine one scenario where user information is stored in a document format, but an important attribute is stored on a separate server that requires per-user authentication. Compare this to a scenario where the data for all users is encrypted and can be stored locally. In one, you are able to download a single block of data and render the entire list of users in milliseconds, with additional details immediately available if you authenticate and get a decryption key. In the other you can only search for users, and potentially not even render them except for the logged in user. All of your calls must be async, because they are all slow, and must be individually designed to accommodate the various ways they can fail. Your UI must constantly deal with partial data, etc.
Fred Brooks said in The Mythical Man-Month: "Show me your flowcharts and conceal your tables, and I shall continue to be mystified. Show me your tables, and I won’t usually need your flowcharts; they’ll be obvious."