• echo64@lemmy.world
    link
    fedilink
    English
    arrow-up
    29
    arrow-down
    1
    ·
    10 months ago

    A native ui wouldn’t have much or any impact on time to show your dashboard. But it would add an astronomical overhead to the development costs

    • Faceman🇦🇺@discuss.tchncs.de
      link
      fedilink
      English
      arrow-up
      7
      ·
      edit-2
      10 months ago

      Yea, we don’t really need first party native UIs (the community can do that themselves), just more control and configurability over what we currently have.

      I’d like to see some better screen formatting options without having to use custom code or unofficial add-ons.

      For example, I’d like to make a grid layout that auto stretches and flows for different display sizes like a modern website can, or lock to a screen width/height etc for a fixed wall mounted controller so I don’t get random scrollbars on some screens.

      And more control over things like tap and hold actions. it’s almost impossible for me to use tap and hold on my main wall mounted display for example, if I move by a single pixel it doesn’t react, I’d like to set the deadzone and delay time for that for example.

    • evo@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      4
      arrow-down
      5
      ·
      10 months ago

      I work in mobile and respectfully disagree with it having no impact on time to show. You might not notice much difference if you are inside your house using gigabit WiFi, but go load your dashboard on a slow 3G/4G network lol

      Sure, there is a higher development cost but you get what you pay for in this case. The project already supports native apps for Android, iOS and Mac.

      • dyc3@lemmy.world
        link
        fedilink
        English
        arrow-up
        8
        ·
        10 months ago

        That makes no sense. Are you are implying that somehow going native gets you faster network transmission speeds?

        Besides, the dashboards in home assistant are heavily customizable with css, which means that just using native components is not practically feasible.

        • evo@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          3
          arrow-down
          2
          ·
          10 months ago

          Are you are implying that somehow going native gets you faster network transmission speeds?

          No. If the components are native they can be loaded immediately without network transmission. The network calls for the current status of entities can happen in parallel and would complete much faster than one large webpage load.

          And your standard cards can not be modded with CSS unless you install something 3rd party that allows that.

      • echo64@lemmy.world
        link
        fedilink
        English
        arrow-up
        4
        arrow-down
        2
        ·
        10 months ago

        The native apps are functionally webapps, they are not “native”. You should be able to tell that if you “work in mobile”.