• it seems like supporting the back button widget is the intended way forward

    Yes, absolutely!

    However, the Weather app already calls for the clock UI, which sounds like it'd conflict with using Bangle.setUI({mode : "custom", back : function() … }) to provide a back button.

    I think it would still work fine. I just tested:

    Bangle.setUI({mode:"clock",back:function­() {
      Bangle.showClock();
    }});
    

    And I think that's good. I'm not really sure I understand the reasoning behind making the weather app behave differently to every other app (going to launcher instead of the clock) but my preference would be to make 'back' go back to the clock.

    Maybe we need some kind of UX guideline in the docs regarding the use of the back button?

    Yes, I guess this might clear things up? I'm just wary of adding to the existing pile of documentation when it seems not that many people read it anyway :)

    Or a default implementation going back to clock or launcher (configurable?).

    I think we'd already discussed this in a PR? Afaik nothing stops someone from making a one-line custom boot code app that does Bangle.showClock = Bangle.showLauncher if this is what they really want.

  • I'm not really sure I understand the reasoning behind making the weather app behave differently to every other app (going to launcher instead of the clock)

    Probably because I just copied it from some clock code without thinking too much about it ;-)
    And after that we just kept preserving existing behaviour, which is how we ended up with Bangle.setUI("clock");delete Bangle.CLOCK;

    my preference would be to make 'back' go back to the clock.

    Yes, I agree.
    Maybe we should even add a Bangle.setUI("app") mode, where the middle button goes back to the clock?

About

Avatar for rigrig @rigrig started