Question

Does it change anything to write :

@Override
protected void onDestroy() {
    MydbHandler.close();
    super.onDestroy();
}

Or

@Override
protected void onDestroy() {
    super.onDestroy();
    MydbHandler.close();
}

Answer 1

The general recommendation is:

• For lifecycle methods with clear “creation” semantics (e.g., onCreate(), onStart(), onResume()), chain to the superclass first

• For lifecycle methods with clear “destruction” semantics (e.g., onPause(), onStop(), onDestroy()), chain to the superclass last, after any of your work

• For everything else, it hopefully does not matter unless documented otherwise

Hence, it’s generally better form to use your first snippet. That being said, I am not aware of any actual problem with your second snippet — in fact, I used that same approach for my first couple of years of Android development.