Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6765693
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 26, 20262026-05-26T14:44:31+00:00 2026-05-26T14:44:31+00:00

Do you always call finish() on some activity before going to another activity? For

  • 0

Do you always call finish() on some activity before going to another activity?

For example, in order to prevent user going to the previous activity via mobile back button, some people suggest that you should finish all activities, except the main one. This way, the back button always returns you to the main activity (or any other activity you think a user should be navigated). This is done by overriding back button behaviour.

Bad thing of this is when there is a dialog run from the Handler which try to runs after the activity finished (http://dimitar.me/android-displaying-dialogs-from-background-threads/).

What is your rule of thumb on this issue? Call finish() in some smarter way or overriding back button to direct user to page of your choice?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-26T14:44:31+00:00Added an answer on May 26, 2026 at 2:44 pm

    If you understood the workflow of an Android application, there should be no need to override the back-button (except for some special cases like Games for example).

    If you don’t want the user to get back to the previous Activity, finish it. There should be no need to override the back-button for that.

    public class Activity1 extends Activity{
    
        // Some onclick-Handler
        public void onButtonClick(View v){
            Intent i = new Intent(this, Activity2.class);
            this.startActivity(i);
            // Don't want you to return:
            this.finish();
        }
    }
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Does startActivity() always call through to startActivityForResult()? Example: public class ActivityTest extends Activity {
For some reason, when I use the call, the result is always returned as
I find that I frequently end up writing a function that I always call
When I call the PrivateFontCollection.AddFontFile method in Mono.net It always returns a standard font-family.
I always believe they did, but seeing some answers here make me doubt... Can
Can I somehow force a derived class to always call the overridden methods base?
The Castle wiki says at several places I should ALWAYS call container.Release() for components
I always call it the arrow operator , but I'm sure it has an
The Cocoa framework has a convention to always call self = [super init] in
Possible Duplicate: Why doesn't the CLR always call value type constructors Found next code

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.