Introducing GUIDE

Dreamweaver for Android


GUIDE’s simple WYSIWYG user interface allows you to use all the gestures that are common to content creation apps like: Apple KeyNote, OmniGraffle and Adobe Illustrator. If you’ve used tools like this before, you’ll pick up the basics of using GUIDE to create user interfaces for the Android platform in minutes.


GUIDE’s layout editor provides a fully ‘free-form’ experience for editing Android layouts. By free-from, we mean that you can arrange the components as you would in any other content creation app. Move components by selecting them with the mouse and dragging them. Resize components by dragging their resize handles. Copy components with copy-paste. Just as you’d expect.
While you are working on your design, GUIDE’s patented layout inference engine figures out how to configure Android’s layout system to produce a faithful copy of your design.


The secret to making designs fully responsive lies in giving designers and developers effective ways to see how their layouts behave as the aspects of their deployment environment change. Screen size is top of this list and GUIDE allows the corners of its virtual device to be dragged around with the mouse so that you can sweep through entire ranges of possible devices in seconds. Meanwhile, GUIDE’s highly tuned rendering pipeline is at work to show exactly how the design will layout and render on each of these devices in real time.


GUIDE’s patented rendering pipeline is 100x faster than the rendering pipeline used in Android Studio’s native Layout Editor. By using this new rendering technique, GUIDE is able to render your design in real time rather than using jarring visual metaphors such as bounding boxes during the more expensive parts of layout manipulation. GUIDE’s rendering pipeline uses the same code as regular Android on a real device and monitors the state of the layouts so that it can warn the user of failing layouts as things get too small. In providing visual feedback of the actual design, developers and designers can see the precise point at which a layout has too much content for the size of display and can put a more compact design in the appropriate Android size bucket to make their overall design properly responsive.


While GUIDE operates on standard Android layout XML files, our view is that the right editor for layout files is a Layout Editor – not an XML Editor. You can still use Android Studio’s excellent XML editor to edit aspects of the layout file that have nothing to do with layout; like internationalisation support and providing the ids that are required for programmatic access. In these cases, GUIDE accommodates two-way editing so that changes to non-layout related state are respected and preserved during GUIDE’s manipulation of the layout parameters that are stored in the same file.