如何让菜单在所有Activity中生效？避免重复编写代码

Great question—duplicating menu setup and click handling code across every Activity is such a tedious pain point that every Android developer has faced at some point. Let’s break down two clean, scalable solutions to eliminate that repetitive boilerplate:

1. Create a Reusable Base Activity (Classic, Simple Approach) #

The most straightforward fix is to build a base Activity class that encapsulates all your menu logic, then have all your other Activities inherit from it. This way, you write the menu code once and reuse it everywhere.

Example Base Activity Code: #

public class BaseMenuActivity extends AppCompatActivity {
    @Override
    public boolean onCreateOptionsMenu(Menu menu) {
        // Inflate your shared menu once here
        getMenuInflater().inflate(R.menu.menu_main, menu);
        return true;
    }

    @Override
    public boolean onOptionsItemSelected(MenuItem item) {
        // Handle all shared menu clicks in one place
        switch (item.getItemId()) {
            case R.id.action_settings:
                openSettingsScreen();
                return true;
            case R.id.action_search:
                launchSearch();
                return true;
            case R.id.action_profile:
                navigateToProfile();
                return true;
            default:
                return super.onOptionsItemSelected(item);
        }
    }

    // Make these methods protected so subclasses can override them if needed
    protected void openSettingsScreen() {
        startActivity(new Intent(this, SettingsActivity.class));
    }

    protected void launchSearch() {
        // Implement your shared search logic here
    }

    protected void navigateToProfile() {
        startActivity(new Intent(this, ProfileActivity.class));
    }
}

How to Use It in Your Activities: #

public class HomeActivity extends BaseMenuActivity {
    // No need to rewrite onCreateOptionsMenu or onOptionsItemSelected!
    // If you need to add extra menu items for this specific Activity, just override the method:
    /*
    @Override
    public boolean onCreateOptionsMenu(Menu menu) {
        super.onCreateOptionsMenu(menu); // Keep the shared menu items
        getMenuInflater().inflate(R.menu.menu_home_extra, menu); // Add Activity-specific items
        return true;
    }
    */
}

2. Use MenuProvider (Modern AndroidX Recommended Approach) #

If you’re using AndroidX, the MenuProvider API is a more flexible, decoupled alternative to base classes. You can encapsulate your menu logic into a reusable provider class and register it in any Activity (or even Fragment) without needing inheritance.

Example Reusable Menu Provider: #

public class AppSharedMenuProvider implements MenuProvider {
    private final Context context;

    public AppSharedMenuProvider(Context context) {
        this.context = context;
    }

    @Override
    public void onCreateMenu(@NonNull Menu menu, @NonNull MenuInflater menuInflater) {
        menuInflater.inflate(R.menu.menu_main, menu);
    }

    @Override
    public boolean onMenuItemSelected(@NonNull MenuItem menuItem) {
        int itemId = menuItem.getItemId();
        if (itemId == R.id.action_settings) {
            context.startActivity(new Intent(context, SettingsActivity.class));
            return true;
        } else if (itemId == R.id.action_search) {
            // Handle shared search action
            return true;
        }
        return false;
    }
}

Register the Provider in Any Activity: #

public class DetailsActivity extends AppCompatActivity {
    @Override
    protected void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
        setContentView(R.layout.activity_details);

        // Register the shared menu provider, tied to the Activity's lifecycle
        getMenuInflater().addMenuProvider(
            new AppSharedMenuProvider(this),
            this,
            Lifecycle.State.RESUMED
        );
    }
}

Bonus: Customize for Specific Screens #

If some screens need to hide certain menu items, you can add logic to the provider (e.g., pass a flag in the constructor) or override the menu setup in the Activity after registering the provider.

Both approaches eliminate copy-pasted code—choose the base Activity if you prefer a simple inheritance pattern, or MenuProvider if you want better decoupling and compatibility with modern Android architecture components.

内容的提问来源于stack exchange，提问作者Angelbreath