![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png){kind=small}
Issues: Mobile access
Dec. 5th, 2018 07:32 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
recently_foldedThere was some mention of this in greywash's master thread and its comments.
A lot of the concern has to do with the fact that for a mobile ap to be listed in the two major ap repositories, it has to be squeaky clean and have nothing to do with what the repositories view as porn—which is basically all that fandom considers adult content, marginalized communities, gay content, etc. There are ways around this, but they tend to be obscure for many users.
Is this a make/break issue for a new fandom home? Is a mobile-optimized site meant to be used in a device's existing browser ap adequate given the adult content issue? Is creating a mobile ap best left to someone outside the new fandom home?
greywash's master thread and its comments. A lot of the concern has to do with the fact that for a mobile ap to be listed in the two major ap repositories, it has to be squeaky clean and have nothing to do with what the repositories view as porn—which is basically all that fandom considers adult content, marginalized communities, gay content, etc. There are ways around this, but they tend to be obscure for many users.
Is this a make/break issue for a new fandom home? Is a mobile-optimized site meant to be used in a device's existing browser ap adequate given the adult content issue? Is creating a mobile ap best left to someone outside the new fandom home?
