3 ms·
How do you think of #1 in the context of a web app? Each page is essentially a different entry point into the code. I guess the landing page or authentication
by smugma 4y ago
How do you think of #1 in the context of a web app? Each page is essentially a different entry point into the code.
I guess the landing page or authentication page could be considered the equivalent, but I’m not sure those would hit your goals to understand flow of data, etc. ?
- buro9 4y agoIt makes even more sense for web apps. It will tell you how it came to be that a web page received the request, what context it has, how the cookie is resolved to an auth context, how to access any query args, what is available to support the page.
- muzani 4y agoYup, I've stopped looking for the entry point in SPAs and apps. Often the navigation flow can be extremely convuluted. Android introduced navigation graphs [1], which were meant to solve this problem. But what happened in reality were instead of arrows point to each screens, there would be multiple islands that were teleported in from random places. [1] https://developer.android.com/guide/navigation/navigation-getting-started https://developer.android.com/guide/navigation/navigation-ge...