• Replies 8 replies
  • Subscribers 17 subscribers
  • Views 1129 views
  • Users 0 members are here
Options
Related

Enhancements to the Connect IQ Store (Apps descriptions)

Former Member
Former Member over 9 years ago
In general the format of apps descriptions is nice and conform, but I propose the following enhancments supporting better apps descriptions:

  • It should be possible for the app author to add some minor formatting in the Description box. E.g. subsections, lists, Bold fonts etc. URL handling can be improved.
  • A formatted 'Change Log' box should be added to the update page.
  • It should be possible to include an illustration in the Description box. An illustration (photo) is not a screen shot of a watch. A good illustration may sometimes explain more than 1000 words. The aspect ratio of an illustration is not restricted to 1:1. However a file size restriction is needed. In order to improve conformity the height of the illustration can be limited to 400 pixels in order to be conform with photos in the screen shots section.
  • The order of the screen shots displayed in the app store should be defined by the app author. In the app store the order of the picture seems fixed but different from the upload sequence. (image1, image2, ..., image5)
  • over 8 years ago
    This is long overdue indeed, I'm surprised no one replied to this!

    The app descriptions look like one big pile of unformatted text (which they are..) and are not very pleasing to look at. This, in turn, might also cause users to not read the description carefully and run into problems..
  • over 8 years ago
    Numbers 1 & 2 are currently being addressed, but I'm not sure about 3 & 4. I'll get those reported.
  • over 8 years ago
    I've just submitted my first app and the lack of formatting is a handicap to writing a decent description. Something like Markdown support would be great, is there any progress on this?
  • over 8 years ago
    We've address image ordering already, and we have a task to add markdown support (which is what I would like to see as well), but it's not yet being implemented.
  • over 5 years ago in reply to Brandon.ConnectIQ

    4 years later (at least) and the things that have been worked on are still not added? Any reason for that?

  • over 4 years ago

    Just submitted my first app, the description text is spartan at best. I can't even group text blocks. Text appears fine in editor, but in the app page its broken. Does anyone know how the parsing is done. e.g. what defines a paragraph?

  • over 4 years ago in reply to André Zunido

    A paragraph is no more than hitting "enter" at the end of a line

    If I enter this as a description:

    This is what a user sees:

  • over 4 years ago in reply to jim_m_58

    Thanks for the input. I didn't really explain myself very well. I wanted to add more than a line break between groups.

    Description


    Features

    - This app has feature A.
      Which has caveat C.

    - This app has feature B.

    The text "Which has caveat C" will lose all whitespace that pads it to the bullet that it belongs (which is already a work-around to the absence of sub-bullet points). Plus it will be separated from the above bullet as if it was another paragraph (as you mentioned, each line is a paragraph).
    I find it tricky, because the editor is not of the WYSIWYG variety, making it trial and error to find something that conveys the required hierarchy to the points.

    But I will try to find something that works. I want to have a mini-manual in the description, and I'm afraid this makes it confusing to follow.