Please add 'path' support to svg in Fitbit OS. There is a large library of svg objects that use mostly 'path' elements to define them freely available on the web. By adding support for this, we could create a richer user experience.
It would also be easier to use 'path' elements to draw certain objects that currently require image files (e.g. images of a heart, footsteps, stairs etc.). Image files also use more memory than would be required by an equivalent svg 'path' definition.
Svg 'path' is also more flexible than an image. For example, there are currently two 'heart' images in Fitbit OS. One is a solid heart while the other is a heart outline. Both of these could easily be reproduced using a single svg path element and changing a single attribute to switch between a solid or outline heart.
Svg elements can also be scaled and rendered any size without losing quality. Currently, if you want differently sized images, you will either have a 'large' image that is then scaled down to the required size, or several differently sized images. Both of these options would require more memory than a path definition.
Moderator Edit: Clarified subject
Join us on the Community Forums!
Community Guidelines
Learn the Basics
Join the Community!
Not finding your answer on the Community Forums?
Go to the Help Site
Contact Support