JI_UI

The Cross-Platform -&- Cross-Language UI Framework:

• Deploy to web and across numerous platforms using your favourite WebFramework.
• Eliminate the need for JSON thanks to gRPC.
• Support multiple programming languages (in backend, or frontend) thanks to gRPC

Preset Status:

✅	❌	❌	❌	❌	❌

✅

✅

✅

❌

❌

❌

❌

❌

❌

❌

❌

❌

Why

• 🏃 Fast & Easy Production: Preconfigured Hot Reload for rapid preview during the production stage.
• 📁 Includes a FileWatcher that automatically compiles .proto files, streamlining development.
• 📝 Automatically generates templates for new gRPC services and message types, accelerating development.
• 👀 Interacive Webview Panel in VS Code via Extension.
• 📱 After the production stage, the extension can build your Native applications.
• 🚀 Automatically implements childProcess in your native app to communicate with your backends without the need for servers
• 🌐 Develop microservices before cloud deployment => easy transition to cloud environments when required.
• 📡 Run UI applications directly on microcontrollers, such as Arduino, without consuming excessive RAM.

Get Started

Method	API	Extension	Project
Quickstart	npm (upcoming)	VS Code Marketplace (upcoming)	Initialize via Extension
Git Pull	clone and copy Api Folder	clone and copy Extension Folder	clone and copy ExampleProject

How it Works

gRPC enables efficient communication between the client and server. It uses Protobuf for defining services and message types, providing strong type safety and easy integration across different programming languages. A Web Proxy, such as gRPC-Web, allows communication between a web browser and a gRPC server. By using gRPC and Protobuf, you can write services and applications in various programming languages. This allows for cross-platform compilation, as gRPC implementations are available for each language. By using a gRPC-Web proxy, you can directly integrate your gRPC services into web applications. A non web-Endpoint server serves as the backend for your application. It can host gRPC services and act as an interface to other backend services. The JI_UI API creates a wrapper for your Endpoints, Protofiles and Scripts that use the Protobuffs. Protobuffs for many available languages are getting created using my protoc-repo. it uses compiled protoc binary with javascript Language specific Presets can be picked and added to your Code via API and Code Extension.

graph TD;
    Frontend["🌐 Frontend (React, Vue, Angular, etc.)"] --> go_backend;
    Frontend -->|webView| webView[🖥️ Browser]
Frontend -->|webView| code[⚙️ VS-Code]
    Frontend -->|nativeBuild| nativeBuild[📲 App] 
    go_backend --> |microservice|Backend;
     nativeBuild-->|childProcess|Backend;
    JI_UI --> go_backend;
    JI_UI --> protobuffctl;
    protobuffctl --> JI_UI;
    JI_UI --> Frontend;
    JI_UI --> |config|Backend;
    
    subgraph go_backend [🌟 go-ServiceMesh]
        gRPC_webProxy --> gRPC_Server;
        gRPC_Server;
    end
	subgraph JI_UI [🕹️ JI_UI]
Extension;
API;
end

    subgraph protobuffctl [🗄️ protobuffctl]
        Api;
    end

    style JI_UI fill:#f9d71c,stroke:#333,stroke-width:2px
    style go_backend fill:#039dfc,stroke:#333,stroke-width:2px
    style protobuffctl fill:#03fc9d,stroke:#333,stroke-width:2px

Loading

Api

• upcomming

Extension

• upcomming

Motivation

In my search for a tool that perfectly meets my needs... This led me to start developing a cross-platform UI framework, designed with a React/Web-based frontend and a backend using a higher-level language. This framework is built to make cross-compilation easy, with gRPC playing a key role, ensuring compatibility within containers (if needed) and simplifying the development of microservices outside of cloud environments.

🚀 Advantages of Using Go as a Backend

Performance and Scalability: Go is renowned for its high performance and efficiency, especially in handling network requests and resource management. This makes it an ideal choice for backend services that need to handle high loads.
Constant Runtime: Go applications have a constant runtime, meaning they are not affected by the number of concurrent requests. This is crucial for backend services serving a large number of simultaneous users.
Security: Go offers a robust standard library with many security features, including support for HTTPS, prevention of Cross-Site Scripting (XSS), and SQL Injection. This is essential for the security of backend services.
Simplicity and Maintenance: Go applications are generally simpler to configure and maintain than complex backend architectures based on multiple technologies. This reduces complexity and improves maintainability.
gRPC Support: gRPC is a high-performance RPC framework developed by Google. It supports efficient communication between clients and servers and multiple programming languages, including Go. Using gRPC can significantly improve the performance and scalability of backend services.
Efficient Network Management: Go provides efficient mechanisms for network management, including support for HTTP/2 and gRPC, which can reduce network load and improve performance.
Excellent Support for Microservices: Go is excellent for developing microservices, as it is lightweight and supports easy deployment. This is particularly useful for modern, scalable backend architectures.
Global Variables and Static Typing: Go offers global variables and static typing, which can simplify the development and maintenance of backend services. These features can help reduce errors and improve code quality.

🌐 Advantages of Using React with gRPC

Efficient Data Handling: React is a powerful library for building user interfaces, but when combined with gRPC, it can efficiently handle data in real-time. gRPC's support for streaming and bidirectional communication allows for a seamless data flow between the client and server, enhancing the user experience.
Type Safety: gRPC uses Protocol Buffers (protobuf) for defining services and message types, which provides strong type safety. This means that the data structures are defined once and used across the client and server, reducing the risk of errors and improving the maintainability of the code.
Performance: gRPC is known for its high performance, especially in terms of speed and efficiency. It uses HTTP/2 for transport, which allows for multiplexing, lower latency, and header compression. This can lead to faster load times and a smoother user experience in React applications.
Streaming Support: gRPC supports streaming, which allows for real-time data updates without the need for polling. This is particularly useful in applications that require live updates, such as chat applications or real-time analytics.
Language Agnostic: gRPC is language-agnostic, meaning it can be used with any programming language that supports gRPC, including JavaScript for React applications. This allows for a flexible development environment and makes it easier to integrate with other services or components.
Interoperability: gRPC is designed to be interoperable, meaning it can work with a wide range of systems and services. This is beneficial for applications that need to integrate with existing systems or services, as it reduces the need for custom integrations.
Security: gRPC supports transport security with TLS, ensuring that data transmitted between the client and server is encrypted. This is crucial for applications that handle sensitive information.

---

Code Snippets (minimal example)

proto file (protobuffs are in example project folder)

syntax = "proto3";
option java_multiple_files = true;
option java_package = "io.grpc.examples.helloworld";
option java_outer_classname = "HelloWorldProto";
option objc_class_prefix = "HLW";
option go_package = "github.com/ji-soft/ji_ui/protos";
package ji_ui;
// The greeting service definition.
service Greeter {
  // Sends a greeting
  rpc SayHello (HelloRequest) returns (HelloReply) {}
  rpc SayHelloStreamReply (HelloRequest) returns (stream HelloReply) {}
}
// The request message containing the user's name.
message HelloRequest {
  string name = 1;
}
// The response message containing the greetings
message HelloReply {
  string message = 1;
}

React frontend

import React, { useState } from 'react';
import { GreeterClient as Greeter } from './ui_pb_service';
import { HelloRequest,HelloReply } from './ui_pb';

const App = () => {
 const [message, setMessage] = useState('noMesg');
 const [name, setName] = useState('not set');
 const [inputValue, setInputValue] = useState('not set');
 const handleInputChange = (event) => {
  setInputValue(event.target.value);
};
const handleSubmit = (event) => {
  event.preventDefault();
  setName(inputValue); 
};

 const sendHelloRequest = async () => {
    const client = new Greeter('http://localhost:8080'); 
    const request = new HelloRequest();
    request.setName(name);

    try {
     client.sayHello(request,function(err, response) {
        setMessage('MSG from GO BACKEND :'+ response.getMessage());
     });
    } catch (error) {
      console.error('error while sending:', error);
    }
 };

GO backend

// server is used to implement helloworld.GreeterServer.
type server struct {
	pb.UnimplementedGreeterServer
}

// SayHello implements helloworld.GreeterServer
func (s *server) SayHello(ctx context.Context, in *pb.HelloRequest) (*pb.HelloReply, error) {
	log.Printf("Received: %v", in.GetName())
	return &pb.HelloReply{Message: "Hello " + in.GetName()}, nil
}

func main() {
	flag.Parse()
	lis, err := net.Listen("tcp", fmt.Sprintf(":%d", *port))
	if err != nil {
		log.Fatalf("failed to listen: %v", err)
	}
	s := grpc.NewServer()
	pb.RegisterGreeterServer(s, &server{})
	log.Printf("server listening at %v", lis.Addr())
	if err := s.Serve(lis); err != nil {
		log.Fatalf("failed to serve: %v", err)
	}
}

---