![]() Even things you might not think are important, such as spelling and grammar errors, can cause your app to be rejected. You might be OK with the short and long description of your app being the same – but it’s an instant fail. These must be useful, accurate and of a good standard. Mind your languageĪnother place where the Teams Store team maintain high standards is around how your app is described, via the descriptions and other manifest properties. ![]() Your app will be run thoroughly by real people, so it needs to do what it should, every time. This is not the place for “fake it till you make it, ship it now and we’ll fix it later”, and you should not start the validation process until you are 100% ready. Broken links, apps that crash, confusing or nonsensical error messages all add up to a poor user experience, and the Teams Store team have a quality gate to stick to. This sounds like a no-brainer, but lots of apps get rejected because things aren’t working correctly. ![]() Some of them seem really basic (like the first one) but. I’m not going to talk about them all, but I do want to highlight ones that I see people missing, or that aren’t always obvious unless you’ve experienced them.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |