The most prominent pain-point on CabloyJS: Through modular architecture, multi-scenario
business can be rapidly developed
scenario | Frontend | Backend |
---|---|---|
PC: Web | CabloyJS Frontend | CabloyJS Backend |
PC: Exe | CabloyJS Frontend + Electron | CabloyJS Backend |
Mobile: IOS | CabloyJS Frontend + Cordova | CabloyJS Backend |
Mobile: Android | CabloyJS Frontend + Cordova | CabloyJS Backend |
Slack | CabloyJS Frontend + Slack API | CabloyJS Backend |
CabloyJS Frontend + Wechat API | CabloyJS Backend | |
Wechat Enterprise | CabloyJS Frontend + Wechat API | CabloyJS Backend |
DingTalk | CabloyJS Frontend + DingTalk API | CabloyJS Backend |
frontend and backend separation
, only one set of CabloyJS backend code should be developedThe most prominent bright-point on CabloyJS: Through the style of pc = mobile + pad
, the UI interaction experience
and development mode
of the mobile scene are brought into the PC scene. It not only significantly reduces the amount of code development and improves the efficiency of development, but also maintains the consistency of user manipulation experience
In the large-scale web business system, it is inevitable to include a large number of businesses and functions. The adoption of modularization
will bring the following advantages:
frontend and backend separation
, fully release the ability of the backend APIs and support the deep customization and development of the frontend