All following about Structor (of which I'm apart of).
Imagine you should start a greenfield project for a Web app with modern UI (for example, a new micro service, which will have a Web app for the administration purpose).
And imagine, you have a starter-kit with a bunch of ready to use React UI components along with infrastructure for a Web app (for example, react-redux-starter-kit, but with React Bootstrap and React Widgets libs inside).
In addition, you have a tool, which allows visually combine any type of components on the Web page. Moreover, this tool has an ability to generate a scaffolded source code for UI components connected to any kind of frameworks like Redux, Relay, etc. (with actions, reducers, routes, so on…).
The tool automatically compiles all new source code and reuses all generated components on the page.
Of cause, you are not limited in editing the source code of the project in your favourite IDE, because compiler and hot-loader will patch pages with your changes in tool's workspace.
Would you like to use such a tool in your project?
And if yes, what type of the scaffolds for the source code you would like to use?
a) Infrastructure generators:
Generate REST service with Swagger docs by entered Swagger configuration format.
Generate GraphQL server by entered data structure in GraphQL schema format.
b) Component generators:
Generate Redux wrapped components connected to existing REST API.
Generate Relay wrapper components connected to existing GraphQL server.
The basic idea being to visually compose applications and fill in the gap with code that glues things together. The benefit with such approach is that the tool does the architectural heavy lifting so that a moderately skilled programmer can implement sophisticated business applications with ease. Think excel for business software that isn't visual basic.
Looks interesting. "Marketplaces" are always tricky because the quality is so uneven. Usually like to see which components are produced by the core team, or at least which are "vetted".
The "Reactiflux" community sent enough messages as to make search on Slack's free plan effectively useless (since old messages would expire within minutes or hours). I understand that Discord plans to add search.
Incidentally, why do people prefer native apps instead of browser based on the desktop?
Is it because the tab is hard to find on the browser...or is there a specific advantage to the native client?
I find it jarring when people use desktop clients over browser...especially when it is very likely that most of the engineering teams at these startups are most likely web based.
Don't the desktop apps lag in features behind their web interfaces?
In the case of Discord, the desktop app is an Electron wrapper around the web app with additional native features. For example, the native client adds better voice support (i.e. push to talk w/o needing browser focus), native notifications and an in-game overlay.
