• State Not Answered
  • Replies 5 replies
  • Subscribers 19 subscribers
  • Views 287 views
  • Users 0 members are here
Options
Related

Different watch screen sizes support

STeN
1 month ago

Hello,

I am working on watch app that supports the SDK 3.2.0 an newer, which I consider as a good base (feel free to correct me if I am wrong). That means supporting a variety of different screen sizes hence image resources in different sizes.

I have grouped them into 5 categories based on display size:

  • The larger size is smaller or equal to 176px
  • The larger size is smaller or equal to 240px
  • The larger size is smaller or equal to 280px
  • The larger size is smaller or equal to 390px
  • Anything larger than that

Do you consider it a good?

To get better overview of the sizes and to be able to prepare the bitmaps in correct sizes I have drawn in script all resolutions into a single image, here is the link: https://gcdnb.pbrd.co/images/4JlrPI8zEOu8.png?o=1 

Are there any other important resolution I am missing?

Also anything I post does not appear here, but I get the notification "needs to be moderated and has been added to the moderation queue." - this seems to take 24+ hours and probably event more. This kind of makes the discussion impossible:))

Thanks a lot

STeN

  • 0 1 month ago

    Go to the directory where your SDK is. In the Devices directory open the compiler.json, simulator.json of any device, and see where you can find the resolution of the device. Then grep that in all the device directories and you'll have all the possible resolutions. Also note the shapes, tere's rectangle and semi-circle (maybe only in older devices) as well. 

  • 0 1 month ago in reply to flocsy🤠

    The I2 and some I3 devices have a shape of SCREEN_SHAPE_SEMI_OCTAGON  Where the sub screen on some adds an extra twist.

    Here's where you can easily find the screen dimensions and shape:

    https://developer.garmin.com/connect-iq/compatible-devices/

  • 0 1 month ago

    You are missing the Instinct E 40mm which is [annoyingly] 166x166, also this and 163x156 and 176x176 are black and white only, so check how they handle your colors.

    But why not use a single image say, 600x600 and then scaleRelativeTo="screen" so you hit all and should cover any in the future

    EDIT: and as Jim states how will these look / how do you want them to look like on semi-octagon?

  • 0 1 month ago in reply to Tim

    Hi Tim,

    Thanks for an answer!

    > Instinct E 40mm 
    I missed that one! Thanks - 166x166 + B&W + semi-octagon + 128 kB mem - it seems to be the best combination:)

    > But why not use a single image say, 600x600 
    That is surely an option and some devices will share the same size images and I clip out what I need, but I prefer to prescale images manually into several groups incl. the pixel depth (if I ever solve this) in the desktop graphical programs to make sure it is done nicely.

    Future devices is another question - but it anyway requires the submission of the new app version to the store right? So it can be handled case by case.

    Semi-octagonal I need to think about:)

  • 0 1 month ago in reply to STeN

    AGAIN: pixel depth is not enough! You want your pics to only use the colors available on the device, otherwise the whole pre processing makes no sense as the resource compiler will ditter it to match the colors of the device, and then you could just do the same using only the original image