Simplified response Design Froont Now to simplify design sharing

Froont, which launched the WYSIWYG response web design editor Last May, recently ended the survey, and upgraded to a platform for designers to provide a set of responsive web design and community service.

Froont, who launched the beta last year, provides designers with a visual online web design environment. It helps designers to easily create responsive web design, build prototypes, and share them with team members and customers without having to install any tools, but the whole process doesn't need to write any code, but the output is code-HTML/CSS, and all the design material is organized through the code and the cloud.

However, although this tool has been very handy, we have to face the reality that few designers are designed from scratch. They need a template, which is something to refer to.

For designers, previously shared design elements include icons, wordpress themes, UI packages, and even bootstrap or zurb frames. But it's hard to share a whole-site design. The reason is simple-the lack of an open design standard. Froont Although most operations are drag-and-drop, but its output is HTML5/CSS3, and the latter is the open standard of the web. As a result, users can not only display their designs or get inspiration through Froont, but also reuse the design and develop new things on this basis.

Users can choose to share with others via Facebook, after they have designed their own interface by Froont using WYSIWYG technology. For other users, the design that others share will also appear on the Froont page, the user can copy a design of others by clicking Twin, and then make their own design changes on this basis. Designed to support a variety of device sizes, users can see on the page in accordance with the different size of the response design effect.

In short, Froont's visual design platform allows users to copy the entire design and then edit or share the copy to other customers. This should resemble the fork functionality and code sharing functionality of the code-managed platform GitHub. You can think of it as a web designer's github. Although some Web development tools also have design import and export capabilities, these tools are generally paid and need to be installed, and the design still has a lot of raw stuff, which is not conducive to reuse of other platforms. The key is that these tools lack a platform for design sharing. And Froont has these advantages.

In addition, Froont's free value-added business model is ingenious. Non-paid users create pages or micro-sites that are mandatory to share, and any person can copy edit reuse. If the user does not want others to see their results, please pay. This free value-added model is the same as GitHub. Is it possible for Froont to become a designer's GitHub? We wait and see.