Public add-on requirements

When you develop an add-on for public release through the eLabNext Marketplace, there are specific requirements and considerations you must meet. Public add-ons are accessible to all eLabNext users, which means they must adhere to higher standards for quality, documentation, and user experience.

This document outlines the key requirements and responsibilities you have when publishing public add-ons to the eLabNext Marketplace.

Documentation and user support requirements

Comprehensive documentation

Your public add-on must include clear and concise documentation that enables any user to understand your add-on's functionality without prior knowledge. Your documentation should include:

Clear feature descriptions - Explain what your add-on does and how it benefits users
Step-by-step usage instructions - Provide detailed guidance on how to configure, and use your add-on
Prerequisites and dependencies - List any requirements that are present and any setup involved with this.

Visual support materials

You must supplement your documentation with clear images and screenshots that support the written instructions. Your visual materials should:

Indicate where in the ElabNext application the add-on can be found
Demonstrate key features and functionality
Show the user interface and expected outcomes

Active user support

You are required to provide active support for your public add-ons, including:

A designated support contact point for user questions and issues
Timely responses to user inquiries and support requests

Developer responsibilities

Support and maintenance burden

The complete responsibility for support and maintenance of your public add-on falls on you as the developer. This includes:

Bug fixes and issue resolution - You must address any problems that arise with your add-on
Compatibility updates - You must ensure your add-on remains compatible with new eLabNext versions
Manage OAuth - You must ensure authorization tokens are kept up to date for external integration add-ons
Performance optimization - You must maintain acceptable performance standards

Long-term commitment

Publishing a public add-on represents a long-term commitment to the eLabNext community. You should be prepared to maintain your add-on for an extended period and provide adequate notice if you plan to discontinue support.

Review process and quality standards

Enhanced review process

Your public add-on will undergo a stricter and more involved review process compared to private add-ons. This comprehensive review ensures that your add-on meets the high standards expected by the eLabNext user community.

The review process includes:

Functional testing - We verify that your add-on works as intended
Code quality assessment - We review your code structure, security, and best practices
Documentation review - We evaluate your documentation completeness and clarity
User experience evaluation - We assess usability and integration with eLabNext
Security audit - We examine potential security vulnerabilities

Design and styling requirements

Your public add-on must maintain visual consistency with the eLabNext application. Your add-on should:

Use consistent styling, colors, and typography that match the application
Provide a seamless user experience that feels integrated with eLabNext
Maintain responsive design principles for different screen sizes

Development support

Our development team is available to support you throughout the development and review process. We provide:

Guidance on meeting eLabNext design standards
Technical assistance with integration challenges
Feedback on code quality and best practices
Support with documentation and user experience improvements

Don't hesitate to reach out to our development support team during the development process for assistance and guidance.

Partnership opportunities

Explore partnership possibilities

If you are interested in deeper collaboration and expanded opportunities, we offer partnership programs that can provide additional benefits and support for your add-on development efforts.

Get started with partnerships

To learn more about partnership opportunities and how they can benefit your add-on development, you can visit our partner program page:

Scisure Partner Program

Our partnership team will work with you to identify the best collaboration model for your specific needs and goals.

Next steps

Once you understand these requirements and are ready to meet them, you can proceed with Developing your add-on and then move on to the Publishing your add-on process.