QA Requirements for KIK Integration -
blacklist: using kik's blacklist. screen words match blacklist exactly/completely. means, if player nest blacklisted word in more characters before and/or after word, not reject entry. instance, "ahole" rejected, "uraholedood" accepted. q: how restrictively kik's qa need apply blacklist? we're screening exact matches within kik's blacklist.
load time / stopwatch timings: apply load of launch screen? or apply load time of every screen transition? , connection should testing on (eg 3g, wifi)?
thanks!
kik mobile web browser there no qa requirements having website show in browser. i'm going assume referring form of promotion kik (ads, featuring, etc)
kik doesn't have officially documentated blacklist of words. documentation says websites must pg13 show in search or top sites (http://dev.kik.com/build/#search). use judgement in terms of deciding should/shouldn't shown
kik overlays white loading screen on top of websites until javascript
window.onload
event fires. websites should make of effort have users not see screen. stopwatch timings refer screen specifically. again more of general metric difficult estimate average user experience without actual data
Comments
Post a Comment