We can split a larger app into several smaller apps, where the smaller apps are iframed into the main app. This will reduce app size. One potensial performance drawback is that the same data source cannot be used across apps. If there is a key data source that is needed in each of the smaller apps this could result in the same data being read several times. Will this result in an increased number of read operations in the database? Or do appfarm have a way to resolve this where the iframed app can read from the data that exists in the main app?
Hi!
That is an Interesting question.
Loading an app in an iframe can certainly work fine, but the framed apps have no awareness that they are running in a framed context and therefore have no optimizations for it. If you load multiple apps in multiple iframes, it is essentially like opening a separate browser tab for each app (from the server’s perspective).
When an iframe is removed, the app is effectively “closed,” and when it is shown again, it has to be loaded from scratch. So if this is organized as one app per view, for example, it can be disadvantageous to switch back and forth.
When we talk about “splitting apps,” the intention behind that statement is often more about splitting applications according to what a given user group of the solution needs. That shifts the focus toward designing applications around user journeys, etc., rather than a technical concern about the URL never changing. If a given user needs to switch frequently between two surfaces, one should ask whether those two surfaces would ideally belong in the same app.
Hope this helps!
2 Likes
Thank you for the insight. This helps a lot.
1 Like