android - best practice for UI management in app with omnipresent tabbar -


i'm working on android app having visible tabbar.
however, each tab potentially contains many nested "screens".
of course back-button needs handle correctly.

i've spent of day finding out what's best architecture achieve this.
there several similar questions on stackoverflow, couldn't find answer working me. 2 proposals found , tried out:

  • switch view, see here
  • work activitygroup, see here

another approach thought implement "screens" normal activities , have them have own tabbar (but looking same, user doesn't change).
i've seen should possible without redundant code using include statement in layout xml , maybe create common base class "customactivity" configures tabbar.

however since i'm not yet experienced android, wanted ask here before spending more time try , error style.
approach makes sense? if not, better solution?
btw: proposals mentioned above didn't work me because neither button worked me.

thanks every input!

use fragments api, activitygroup seems deprecated.


Comments

Popular posts from this blog

c# - how to write client side events functions for the combobox items -

exception - Python, pyPdf OCR error: pyPdf.utils.PdfReadError: EOF marker not found -