Advertisement
Guest User

Untitled

a guest
Oct 14th, 2019
97
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.54 KB | None | 0 0
  1. Regarding offer details for Presale offers:
  2.  
  3. 1. http://puu.sh/Esqy8/5d73a35a3c.png
  4. Left is from document, right is currently on Android.
  5. The text "To buy tickets you'll need an exclusive presale code before you can purchase on Ticketmaster." is currently hardcoded in the app. What about the new text?
  6. The "12th September at 9am" seems to be dynamically placed. Will it come with the above text as a whole from the API or do we hardcode everything and dynamically put the date there? If so, I'm guessing *musicPresaleStart* should be used for that?
  7.  
  8. 2. http://puu.sh/EsqAn/26e3887eab.jpg
  9. The two paragraphs "We'll send you an SMS and email ...." look similar to the text that we get by clicking on "How do presale tickets work?". Do we use the same text or do we hardcode the two paragraphs?
  10. The part with the "... you can purchase two tickets with each other" seems to be dynamic, thus the confusion.
  11.  
  12. 3. http://puu.sh/EsqHN/ad210498ad.png
  13. 3.1 Currently the text displayed in the popup is the "help" field from the offerDetails json we get from the API. Is this still the case or do we hardcode it and dynamically place the start date?
  14. 3.2 If dynamic text, what is the text when presale has already started? "Presale tickets go live on 12th September at 9am" has no relevance anymore in that scenario.
  15.  
  16. 4. http://puu.sh/EsqVq/1715819c5a.png
  17. Do we display the same hardcoded messages even if the user requested a code ? The text seems to indicate that the user did not retrieve a code, even if he might have done so. Do we just ignore that particular scenario ?
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement