Back Button

IPhones are missing a universal back button. They left it up to the application developers to implement a back button, which is a problem because some applications don’t even implement a back button, forcing users to either get stuck not being able to go back without closing the application, or forcing them to swipe in some direction that we don’t know to go back. Sometimes we’ll get stuck on a page completely not being able to go back at all. Anybody who is not pro back button has not ever used an android phone before and therefore does not understand why this is so beneficial for the user interface. A universal back button serves so many different purposes, if there is nothing to go back to it will just bring the user to the homepage, it will close out ads without having you to look for the x button, it allows you to go to the previous screen, it allows you to cancel operations. It serves so many purposes; there is no reason to have this excluded.

iPhone 14 Pro

Posted on Oct 19, 2022 09:51 AM

Reply
Question marked as Top-ranking reply

Posted on Oct 20, 2022 12:30 AM

Having a back button has little to do with necessity and more to do with convenience and common sense. Without a back button, people are constantly trying to figure out where, and how to go back within each app because each app goes back in a different way, forcing the user to go any wild goose chase to find the back button. Going back is one of the most basic things that we have to do all the time while on a phone, and if it is always accomplished in a different way, it will cause the user to constantly waste time figuring out how to go back. Here are many examples. To go back you may have to: swipe up, swipe down, swipe left, swipe right, click on the upper left X button, click on the upper right X button, click on the lower left back arrow, click on the lower right back arrow, swipe up to first reveal a menu and then click the left arrow, swipe down to reveal the menu then click on the left arrow, click on the screen to reveal more menu options then click on the left arrow. Trying to figure out which one it is wastes time and requires MUCH more thinking and movement of the hand, diminishing user experience. To make things even worse, within the same application, there will be different ways of going back depending on which page the user is on within that application, causing going back inconsistencies even within the same application!


A back button also causes an issue with exiting certain functions within the same application. For instance, I am using Google Chrome right now and I want to close the keyboard after I am done writing this reply. On an android phone, all you would need to do is click the back button, but on the iPhone, there is no back button to close the keyboard, so now we try to figure out how to close the keyboard by looking for anything, and everything, swiping down and up in every direction to try to figure out how to close the keyboard, just to waste time finding out that this application requires you to click a tiny not easily seen done button right above the keyboard.


To make things worse we don’t even know what we are looking for, whether it’s a button, an arrow a swipe a hidden menu or a turd on the screen, we constantly try to figure out how to close things, cancel things and go back, all of which is handled by a back button. All we need to do is click the back button on android, and we are done. But to cancel an operation on iPhones, we need to figure out how to do that which is always done differently.


This clearly complicates the user interface even more. A back button is not a necessity, it is a common sense feature that needs to be implemented, just like a right mouse click is to a desktop computer.

Similar questions

2 replies
Question marked as Top-ranking reply

Oct 20, 2022 12:30 AM in response to Phil0124

Having a back button has little to do with necessity and more to do with convenience and common sense. Without a back button, people are constantly trying to figure out where, and how to go back within each app because each app goes back in a different way, forcing the user to go any wild goose chase to find the back button. Going back is one of the most basic things that we have to do all the time while on a phone, and if it is always accomplished in a different way, it will cause the user to constantly waste time figuring out how to go back. Here are many examples. To go back you may have to: swipe up, swipe down, swipe left, swipe right, click on the upper left X button, click on the upper right X button, click on the lower left back arrow, click on the lower right back arrow, swipe up to first reveal a menu and then click the left arrow, swipe down to reveal the menu then click on the left arrow, click on the screen to reveal more menu options then click on the left arrow. Trying to figure out which one it is wastes time and requires MUCH more thinking and movement of the hand, diminishing user experience. To make things even worse, within the same application, there will be different ways of going back depending on which page the user is on within that application, causing going back inconsistencies even within the same application!


A back button also causes an issue with exiting certain functions within the same application. For instance, I am using Google Chrome right now and I want to close the keyboard after I am done writing this reply. On an android phone, all you would need to do is click the back button, but on the iPhone, there is no back button to close the keyboard, so now we try to figure out how to close the keyboard by looking for anything, and everything, swiping down and up in every direction to try to figure out how to close the keyboard, just to waste time finding out that this application requires you to click a tiny not easily seen done button right above the keyboard.


To make things worse we don’t even know what we are looking for, whether it’s a button, an arrow a swipe a hidden menu or a turd on the screen, we constantly try to figure out how to close things, cancel things and go back, all of which is handled by a back button. All we need to do is click the back button on android, and we are done. But to cancel an operation on iPhones, we need to figure out how to do that which is always done differently.


This clearly complicates the user interface even more. A back button is not a necessity, it is a common sense feature that needs to be implemented, just like a right mouse click is to a desktop computer.

Oct 19, 2022 10:50 AM in response to John Dit

15 years Apple has been making iPhones without a dedicated back button.

If it was really required, they would have added it by now.


I've never needed a back button, and yes I have used Android devices, and I find the back button completely unintuitive in an App as I expect all my navigation in an app to be inside an app.


If the app is not providing a way to get back that's an issue with the app.


Design requirements and parameters for iOS apps are all done considering there is no back button. If you think there should be a way to go back in an app, then its specifically a issue with the App, or you are somehow trying to do something in an app that is not expected to be done.


You are however free to give Apple feedback about it at: Feedback - iPhone - Apple


This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Back Button

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.