https://github.com/apigear-io/roadmap

Public discussion of the APIGear issues and the place to share our roadmap. Feel free to suggest new features or discuss existing ones.
https://github.com/apigear-io/roadmap

Last synced: 4 months ago
JSON representation

Public discussion of the APIGear issues and the place to share our roadmap. Feel free to suggest new features or discuss existing ones.

• Host: GitHub
• URL: https://github.com/apigear-io/roadmap
• Owner: apigear-io
• Created: 2020-05-01T12:08:16.000Z (about 5 years ago)
• Default Branch: main
• Last Pushed: 2023-09-28T13:04:50.000Z (over 1 year ago)
• Last Synced: 2025-01-18T11:27:04.205Z (5 months ago)
• Size: 5.86 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 1
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# ApiGear Roadmap

This is a high-level site for planning roadmap and features. We use issue tracking in the projects to track issues for the tooling (cli, hub, studio) and templates.

The information here does not always reflect the same state of thinking.

/ ApiGear Team

## Roadmap Discussion

We worked a lot in 2023 to make all different ApiGear features more stable and easier to work with. At the same time we invested quit a lot into the whole IPC story. For 2024 we will focus more on designer value (e.g. visual editing, better simulation, record-replay) and product visibility (e.g. events, cloud hub, meetups). We still will work in better IPC integration and optimizing performance (change ipc encoder, use ids as symbols).

### 2024 Focus

- Designer Value - We believe our customers are mainly Designers and Managers. They need to find an solution which solves their problem. How to get data into UE, how to simulate backends when they are not there yet, how to record an interaction session and replay it again and again.

    - Visual API Design

    - Record - Replay

    - Cloud Hub

- Manager Value - For managers it will be important to have team sharing, to see API host-spots (e.g. most used APIs), general API usage, etc. This will give them data points when discussing project progress. The out of the box experience needs to allows managers to grasp the understanding of IPC generation. It just works!

    - Out of Box Experience

    - Cli/Studio Certificates

    - API usage statistics

- Project Value - Having an out of the box IPC solution which works for 90% of all use cases and it's fast enough to simulate world movement needs to be the target at some point. With a reference server to validate interoperability between language and performance tests to validate our speed. The most important targets are UE, C++, Go for UE OEM customers.

    - Moving 3D Cube demo on different platforms

    - Server to test language interoperability

    - Visible Benchmark reports

    - Broader api samples

- Visibility - We need to get more visibility for ApiGear. We need to get more people to know about ApiGear and what it can do for them. We need to get more people to use ApiGear and give us feedback. We need to get more people to contribute to ApiGear and help us to make it better.

    - Provide talks on events

    - Talk to customers on a more frequent base

- IPC Optimization - We need to ensure we can support out of the bow a world movement simulation. This means we need to optimize our IPC solution to be fast enough to simulate world movement. We need to ensure we can support UE, C++, Go for UE OEM customers and our tooling. We need to ensure we can support a reference server to validate interoperability between language and performance tests to validate our speed.

    - Research int ID usage instead of string symbols

    - Research API hash to validate versions

    - Provide insights about performance bottlenecks

We will probably not work on all of these topics in 2024. We will focus on the most important ones and try to get as much done as possible.

To make these different features happen, we will step back from the IPC topics and focus more on view-models and the core product.

## Feature Discussion

- [feat001 js-filters ](features/feat001_js_filters.md): Add abilities for template writers to add own custom JS template filters.

- [feat002 record-replay ](features/feat002_record_replay.md): Being able to record and replay API traffic was already much earlier requested by our customers. The feature allows customers to record API traffic and replay it later. This is useful for testing and simulation.