The more I think about the article, the less sense it makes.
Data accuracy and completeness are of course important issues, but if you're going to add measures to improve data quality, that should be done when acquiring and processing the data, not when presenting it. So an app sounds like the wrong place to start worrying about the integrity of the data.
Doing statistics properly is not easy: it's not an intuitive subject and it requires a good mathematical background, a lot of care and some common sense. Here at least the article has a concrete proposal: a review and sign off process. Whether that actually helps depends on the quality of the review: does the reviewer master statistics and is there enough time budgetted to do a thorough review?
I have some doubts about painting data presentation as an ethical issue. While I completely agree that clarity is more important than prettyness, overly flashy presentation is far from the only reason why data might be misinterpreted. Perhaps the app developer doesn't understand the domain well enough; hands-on testing with end users would help in that case. Perhaps the end user doesn't understand the data or the processes the data comes from well enough to be able to interpret it accurately no matter how the app presents it. Perhaps the data is so complex that it is not possible to present it accurately in an app format.