Hubleto 2 - ideas and roadmap

Few months ago we have released the first official Hubleto version. And we already started working on Hubleto 2.

Hubleto 2 is now work in progress and we plan to release it during the year 2027. Most probably in Q2, but let's see what the future will bring.

Read here what we are working on now and what we plan to work next.

Latest React and functional components

Hubleto uses its own React-based UI library (github, npm). In Hubleto 1, the library used older versions of React and all components were class-based.

Now we are completely refactoring this UI to use the latest React and to be functional-based. This is the recommended way of using React it - among other improvements - reduces the boilerplate. For example, new way of creating your custom Form looks following:

import React from 'react';
import Translator from '@hubleto/react-ui/core/Translator';
import { FormProps } from '@hubleto/react-ui/components/fc/FormInterfaces';
import Form from '@hubleto/react-ui/components/fc/Form';
import Input from '@hubleto/react-ui/components/fc/FormComponents/Input';

const componentName = 'FormReview'; // must be the same as the exported const
const parentApp = 'Hubleto/App/Community/Documents';
const T = new Translator(parentApp + '/Loader', 'Components/' + componentName);

const FormReview = (props: FormProps) => <Form
  componentName={componentName}
  parentApp={parentApp}
  model={parentApp + '/Models/Review'}
  urlSlug='documents/reviews'
  title={ {field: 'name', sub: T.translate('Document review')} }
  tabs={ {default: {content: () => <>
    <Input field='id_document' />
    <Input field='id_version' />
    <Input field='requested_on' />
    <Input field='id_requested_by' />
    <Input field='reviewed_on' />
    <Input field='id_reviewed_by' />
    <Input field='comments' />
  </>}} }
  {...props}
></Form>;

export default FormReview;
Example of form for document reviews created as functional React component.

 

Lines of code has been reduced here by more than 60%. The code is easier to read and easier to develop.

Further plans and ideas

We're still working on this React UI refactoring. Once done, we plan to work mostly on:

  • clean up unused code from Hubleto 1
  • integrated Hubleto with more external services and tools
  • optimize for speed and resource handling

Give us your thoughts

Do you have any ideas on how to improve Hubleto? Reach us on our LinkedIn or Reddit.

Thank you for your support.