dodgelord:
u can use the site as a guest or anonymous. Post n comment as anonymous or guest. If ur getting dat error msg

Ok

GREATIGBOMAN:


It's actually necessary.

And good user experience.... Not only single page apps use preloaders.


It helps the user to know something is actually loading in the background and they should be expecting something after the load from server or any action they're trying to perform is complete.

They're different types of that preloader...


Google about it to find out more.

I don’t think you understand what I mean. The loading spinner does not appear when the user clicks a button or submits a form or does something on the page. It appears on the page immediately after the page has been loaded, with some content. The app is a multi page application, which means that to get a new page you have to make a request to the server for the new page. And when that page is loaded, the content will be displayed by the browser. So are you saying that it is a good user experience for a user after waiting for the first time for the new page from the server to wait the second time again when the spinner is on the screen before they can finally view the full page. What ever the page is loading the second time, why not send everything at the first request. Why the round trip? Even the op said it’s not serving any purpose.

GREATIGBOMAN:


U will beg for users tire

yes i will.

GREATIGBOMAN:


U will beg for users tire

yes i will.

Go n do blog

Ezecliff:
Pls � out this forum of mine, feed back is expected

naijaterra

This is very nice bro. Hit me up so we can collaborate. I'd help do the UI/UX.

chukwuebuka65:


I don’t think you understand what I mean. The loading spinner does not appear when the user clicks a button or submits a form or does something on the page. It appears on the page immediately after the page has been loaded, with some content. The app is a multi page application, which means that to get a new page you have to make a request to the server for the new page. And when that page is loaded, the content will be displayed by the browser. So are you saying that it is a good user experience for a user after waiting for the first time for the new page from the server to wait the second time again when the spinner is on the screen before they can finally view the full page. What ever the page is loading the second time, why not send everything at the first request. Why the round trip? Even the op said it’s not serving any purpose.

Spinners aren't only for the first content load. It can be use as a placeholder while an api call is being made. Instead of showing a blank page. Its obviously a good user experience, because you know immediately something is coming.

jikins:


Spinners aren't only for the first content load. It can be use as a placeholder while an api call is being made. Instead of showing a blank page. Its obviously a good user experience, because you know immediately something is coming.

My emphasis is not on the placeholder or spinner itself. If you are making an api call with javascript, you definitely should display a loading state before the data arrives. My point is that the api call was not necessary in the first place, being that the app is a multi page application. If you click on a post, the new page from the server should have the full post details and the header and footer or any other thing that should be on the page. And not to send just the header and footer , then make an api call from the client to the same server to get the post body. The round trip isn’t necessary.

chukwuebuka65:


My emphasis is not on the placeholder or spinner itself. If you are making an api call with javascript, you definitely should display a loading state before the data arrives. My point is that the api call was not necessary in the first place, being that the app is a multi page application. If you click on a post, the new page from the server should have the full post details and the header and footer or any other thing that should be on the page. And not to send just the header and footer , then make an api call from the client to the same server to get the post body. The round trip isn’t necessary.

Thats assuming he is the one handling serving the HTML, CSS and JS.

I don't know what language he used but I am guessing he just coded it with those languages and uploaded it on a server. So the server handles serving of the contents. Hence the loading state is still valid. Except he is handling the server side rendering.