It is currently stated in the release notes about the navigation feature that the field has to be named with one of three possible names. I think it would be better if Canvas were to make a new field type for the navigation feature, simply because those three field names may be used in many cases for which the user does not want directions. If not a new field type, at least including more possible names, such as "Location," or "Coordinates" would be useful. Mapping applications work with GPS coordinates in addition to addresses, and it feels a bit strange putting coordinates into a field named "Address."
-
Official comment
We will continue to iterate on this feature for sure. Putting a control on the web for our Admins to dictate whether this navigation button shows up or not is something we might do down the road. But we wanted to hit a large majority of our customers who do need to travel to an "address" field. Another thing we consider is adding complexity to the product by making features dependent upon an Admin to set them up or configure them.
When we survey our mobile users about a third of the feedback is for functionality that already exists in our platform. Admins just haven't set it up. So that is another consideration for "mobile only" features.
Great feedback! Keep it coming and vote for any changes.
Comment actions -
I agree on this, the navigation-feature is awesome but it's a pity that it depends on the labelname.
As I work in a Dutch-speaking company, the labels on our forms are spelled in Dutch.
It would be great if we could activate this feature in a different way, for example by creating a specific field type or by creating a specific style for the textfield.
Please sign in to leave a comment.
Comments
5 comments