[App/Web] Sharing mechanisms (no virality)
Answered/ImplementedCurrently, there is no easy way to do sharing of challenges/topics/projects on both native apps and web mobile.
Some challenges I face:
1) The project code (both alias or ID) is not shown.
2) e.g. I would like to share the vanity url, e.g. gametize.com/game/demo
Potentially... we can:
1) Take inspirations from e.g. Instagram (https://corp.gametize.com/2019/11/18/carmen/)
2) Use that real estate space for people to report, submit reports, copy link, allow them to share on other ways, or even send to other apps (e.g. instagram)
-
Hi Lee Chuan Xin @Amanda bumping this up for your review - to include the "copy link" option here.
-
Currently, still no way to share 1) Topics 2) Challenges 3) Completions 4) Copy link.
Hope the UX team can consider implementing bit-sized updates, using simplest approach (using the "..." icon), starting off with bringing back at least emailing (which was actually there before, but now replaced with direct messaging to admin).
Lee Chuan Xin Amanda -
The main challenge would be that the meta tags cannot be easily populated for individual pages in ReactJS, which causes the description/image preview of the page to be incorrect or empty when page is being shared in other platforms, especially social media.
If the preview is not a concern, e.g. we can use a placehold description/image, implementing the share function for other pages besides project would be more manageable.
We have noted this request in JIRA for further brainstorming/discussions.
-
Thank you Vicott Wong; I will suggest taking care of the Meta tag/Preview matters for phase 2, so it is not a concern for now.
Please go ahead for implementing Share function, cheers! -
1) Regarding Meta Tag/Preview, updates have continued in the internal discussions at "Sharing functions & Meta Headers/Image/Descriptions for Projects/Topics/Challenges". I have recommended a generic image and copywriting.
2) Regarding Sharer tool: I have updated https://support.gametize.com/hc/en-gb/community/posts/360056097951/comments/360010867331 with an image screenshot, for utilizing (...). Again, bringing up for consideration. Amanda. I am confident this should be an easy change.
-
Hi Keith
Point (2) have been taken into consideration for implementations :D
Please sign in to leave a comment.
Comments
9 comments