• przmk@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    1
    ·
    7 days ago

    It’s slow in general, they’re not using vector maps like organic maps do. I love what OsmAnd does but it’s definitely slower to render and more sluggish to navigate than other maps on my FairPhone 5.

    • goldfndr@lemmy.ml
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      7 days ago

      Yes and no. OsmAnd tends to have far more details to display — more data to display or filter out. I’m guessing that if you had a smaller rendering file (instruction for painting) along with a smaller obf (less data due to prefiltering), it’d be closer to comparable.

      Edit: The link, which addresses slowness with GrapheneOS not experienced with stock ROM, seems to specifically address the (non-stock) FairPhone too.

    • InsertUser@en.osm.town
      link
      fedilink
      arrow-up
      1
      ·
      7 days ago

      @przmk
      They’re both vector based. Purely from usage it feels like OsmAnd is rerendering everything from scratch every time with little caching. If you pan away and pan back it takes effectively the same amount of time to recreate the previously rendered view as a fresh view. This time seems to increase with addition obfs for “live” updates etc.
      When Organic Maps updates slowly it tends to feel like vector tiles “falling back” to lower zoom until more detail is retrieved.
      @goldfndr