Эта страница является переводом страницы ModuleTestAndApprove. Перевод выполнен на 100%.

---

Требования для добавления модулей в iRidium store

Follow the rules given below to place a module in iRidium store
Функциональность:
Модератор отклоняет модули, которые

• падают
• содержат видимые ошибки
• делают не то, что написано в описании
• содержат недокументированные или скрытые функции
• скачивают, устанавливают или запускают исполняемый код
• are «beta», «demo» and «test» versions
• contain advertising and marketing materials
• make incorrect diagnostics or display wrong data about a device
• показывают приложения других разработчиков
• use push-notification incorrectly
• send personal or confidential information in push-notifications
• contain viruses, spam, ads
• use third-party monetization mechanisms
• discharge a battery fast or heat a device
• has nothing to do with controlling a smart device or a service
• допускают нелегальный обмен файлами
• work incorrectly on several panels (except cases when a device limits the work of several panels. In these cases it must be written in the description)
• restore connection to a device after reloading incorrectly
• have memory leaks, that lead to the crach of the app some time later
• have a design that does not follow the style guide

A moderator MAY diapprove modules that

• copy modules that are already placed in the store

Other

• разработчики захламляющие магазин модулей разными версиями одного и того же модуля будут заблокированы.
• modules must ask a user's permision to transfer data about him/her and inform where and why these data will be used.

Technical requirement to a module

• There must be a request for module development in the system of module order
• Модуль должен содержать минимум 1 подустройство
• A module must contain as many subdevices as there are working zones, supported by a device.
• There must be minimally one widget for each subdevice.
• The graphic part of a module must consist of items placed in the gallery.
• Модуль должен содержать такие Actions, Events, Conditions, которые описывают минимальный функционал устройства
• Scripts must be devided into driver, interface and general.
• Driver scripts must not have any mention of the interface part.
• All names in the interface part must have a localization flag.
• Everything in the interface must be written in English.
• To register a module write a correct description in the form of module registration. The description must agree with the developed module.
• Functions with module name space must be used instead of IR name space
• All Remotes must have a version for a smart phone and a version for a tablet.

Rules of module testing before making a module public

Before making a module public do the following :

1. Check that the module name, screnshots and icon are correct.
2. Check all texts. They must be in English and contain no mistakes.
3. Check the module functions. All functional items must work and must not cause errors in scripts.
4. Check that a module understands that connection to a device is lost and shows this information to a user.
5. Check that a module restores connection to a device and continues to work correctly after minimizing and maximizing the app.
6. Check that a module works on 2 panel semultaneously.
7. Check that a module work in the server
8. Check that all Actions, Events and Conditions work.
9. Check if the Setup file is correct and changing settings works correctly
10. Check that a module has and interface design for a tablet and for a smart phone
11. If a module has a text field, check that a keyboard appeares when this field is clicked.
12. Check if a module has memory leaks. To do it, launch a module on a panel and let it work 24 hours. 24 hour later a module must continue to work correctly.