Marketplace for Simple Snippets

Propose an Improvement
, ,
1

Current State:
The marketplace currently offers comprehensive, end-to-end solutions that users can install and customize. While this is beneficial, there’s a growing need for more straightforward, modular components.

Proposed Enhancement:
To enhance usability and efficiency, it would be advantageous to include simple snippets in the marketplace. These could consist of:

  • Basic Connections: Snippets for S3 connections to sandbox environments or MySQL connections.
  • Simple Pipeline transformations: Pre-built pipelines with basic transformations.
  • Code Snippets: Frequently used TypeScript and Python functions.
  • Workshop Apps: Minimalist workshop applications with basic widget configurations.
  • User-Contributed Snippets: An option for users to upload and share their own snippets.

Benefits:
By offering these simple, customizable snippets, users can easily download and build upon them, reducing repetitive work. This approach would also make the platform more accessible to new users, providing them with a comfortable starting point for their projects.

2

@RajKarri, have you used the “Build with AIP” application? It has a few building blocks that you have suggested e.g. data connections to S3, workshop applications for a form or different layouts etc.

3

Thank you for pointing me in the right direction. It seems “Build with AIP” addresses these needs, but I believe there’s room for further enhancement. Here are a few suggestions:

  1. Bucketing: We should consider categorizing items based on the app, perhaps with a checkbox selection on the side.
  2. Availability: Packs/Snippets should be easily accessible next to the app. For example, when creating a data connection, corresponding pre-built packs or templates should be readily available for selection. Code snippets are particularly helpful when located directly beside the editor.
  3. Custom Packs: It might be beneficial to offer an option to share custom or community packs/snippets across users.
  4. Scaling: With the growing number of packs, scaling is essential. For instance, we could have a pack for every type of data connection. However, it’s important to ensure the UI remains uncluttered, which also applies to the suggestion in bullet point 2.

Some of these features may already exist; I’m just highlighting them for consideration.