Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

What is routing? Why is "routing" needed in single page web apps?

Tags:

I understood that routing libraries for SPAs like https://github.com/ReactTraining/react-router help to parse the URL and put the app into a corresponding state of a state machine.

Is there more to routing than this?

Why is routing needed in the first place?

Why are URLs important? For example in a desktop app there are no URLs, so what's the big deal about them in a web app?

like image 398
jhegedus Avatar asked Sep 22 '16 10:09

jhegedus


People also ask

What is routing in web app?

Routing is the mechanism by which requests (as specified by a URL and HTTP method) are routed to the code that handles them. As we've already noted, routing used to be file based and very simple: if you put the file foo/about. html on your website, you would access it from the browser with the path /foo/about. html.

WHAT IS routing in the context of a single page application?

Single-page application generally rely on a router. Routers are made up of routes, which describe the location that they should match. These can be static ( /about ) or dynamic ( /album/:id , where the value of :id can be any number of possibilities) paths.

Do single page applications have routes?

There are two ways to support routing in single-page apps: Hashed URL Paths — We break the URL path with a # (Hash) so that the browser understands it's just a virtual fragment. Ordinary URL Paths (Non-Hashed URL Paths) — The server needs to intercept the request and return the index.

Why will you need a router for your app?

We simply couple a component with a specific route, which makes our root component (normally called App) clear, maintainable and readable. Without router, either the root component or state would be messy and hard to maintain.


1 Answers

I also have this problem: "Why do we need routing?". You can write apps without routing at all. The code can get messy but still, it is not impossible.

My biggest reason for having routing is because if the user hits the Back button of the browser (Forward button as well, for that matter), he will not be navigating within the app. The user might expect to navigate within the app using the history of the different "pages" he loaded previously. Instead, he will be thrown out of the web app. Hitting the Refresh button would also throw him to the root of the app.

From the user's point of view, it is a regular web app (he doesn't need to know how it is designed: SPA or otherwise) and it should work as any web app/website should work. Routing ensures this, doesn't it?

like image 198
Anusha Dharmasena Avatar answered Oct 10 '22 09:10

Anusha Dharmasena