First, thanks for providing such a wonderful platform for no coders. I spent one month on frontend/backend services research, and finally decided to use Backendless. It was a long story.
I am building an app displaying photos. I was able to setup pages and showing single photo and a collection photos. One feature I am trying to do is “two fingers zoom in” on a photo. I wasn’t able to find any documentation on it. Is there a way to do it? Appreciate your help.
Yes, we have a ticket in our roadmap to allow configuring the viewport meta tag, but this has low priority right now and in our plans to completely rework the Settings section to be able to configure:
PWA
favicon
meta tags
extra configs (to use them in Logic)
etc.
However, there is a workaround for that:
create a CustomComponent
use it on required pages, it can be converted into a ReusableComponent
the component can be without any UI, just for modifying the meta tag
in the component code you can programmatically set the required content
Hello @vladimir-upirov ,
I’m really looking forward to see PWA features and meta-tag configurations!
W.r.t. your workaround:
I’m not educated in React-components, so it’s good to see examples. Can you recommend a systematic introduction into this topic?
I can fill in the bundle.js file according to your description. But where to place the code document.querySelector('meta[name="viewport"]').content='width=device-width, initial-scale=1.0, maximum-scale=3.0, user-scalable=yes ? Is this custom code for the OnPageEnter event?
I think, dynamic meta-tag generation will work for the user-scalable property. In general we are really waiting for a static definition of meta tags, so that tools like google or WhatsApp can discover these tags.
I would start from their web site https://reactjs.org/ , but pay attention that custom components do not support JSX syntax, also there is a couple of samples when you create a new custom component
It looks exactly as you described it here. I placed the custom component on a page and the new meta-tag can be seen. All good! I just wasn’t sure about this specific line of code …
Thanks