Adobe Thermo

2 Oct 2007 - 2:08pm
6 years ago
5 replies
364 reads
White, Jeff
2007

Just learned of this, from what little I know it sounds awesome. Anyone else
have any info on thermo?

http://labs.adobe.com/wiki/index.php/Thermo

------------------------------------------

"Thermo" is an upcoming Adobe product that makes it easy for designers to
create rich Internet application UIs. Thermo allows designers to build on
familiar workflows to visually create working applications that easily flow
into production and development.
Features

- Use drawing tools to create original graphics, wireframe an
application design, or manipulate artwork imported from Adobe Creative Suite
tools.
- Turn artwork from Adobe Photoshop, Illustrator, or Fireworks
directly into functional components that use the original artwork as a
"skin".
- Define and wire up interactive behavior, such as what to do when a
user clicks on something, without having to write code.
- Easily design UIs that work with dynamic data, such as a list of
contacts or product information, without having access to the actual data
source. Design-time sample data can be used as a realistic placeholder when
laying out an application, testing interactivity, and choreographing motion.

Applications created in Thermo are Flex applications that can be loaded
directly into Flex Builder, providing a great roundtrip workflow for
designers collaborating with developers. The designer's work can be
incorporated directly into the production application with no loss of
fidelity, and designers can continue to refine the design throughout the
iterative development process.

----------------------------------------
Jeff

Comments

2 Oct 2007 - 2:58pm
Jack L. Moffett
2005

It looks like Adobe is finally going to answer Microsoft's move into
tools for RIA development.

http://tinyurl.com/22clcg

Jack L. Moffett
Interaction Designer
inmedius
412.459.0310 x219
http://www.inmedius.com

Questions about whether design
is necessary or affordable
are quite beside the point:
design is inevitable.

The alternative to good design
is bad design, not no design at all.

- Douglas Martin

2 Oct 2007 - 4:37pm
.pauric
2006

For me, the killer feature for any designer orientated app in the
toolchain is the ability to generate succinct legible code thats easy
for a developer (or designer) to debug.

>From the MacWorld article: "Designers using Thermo don%u2019t have
to write code for their applications, but they can choose to view the
source code and see it in a Flex Builder editor that they can work
with if they want to"

Making note of this ability a year out from release hints to me that
this will be a key aspect of the app.

Concern.. assuming there will be pattern libraries for such apps.
This will enable more intuitive designers out of the closet but does
not, nor should it, provide you with magic UCD skills. The same way
anyone with a copy of Photoshop can make a digital photo look pretty
and make them feel like a professional without having to read up on
what it takes to take professional photos.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from the improved ixda.org
http://beta.ixda.org/discuss?post=21023

2 Oct 2007 - 4:57pm
White, Jeff
2007

"...but does
not, nor should it, provide you with magic UCD skills. The same way
anyone with a copy of Photoshop can make a digital photo look pretty
and make them feel like a professional without having to read up on
what it takes to take professional photos."

Definitely. What I love is the thought of adding rich interactivity to my
mockups w/o the involvement of a developer. I have not been writing code for
about 7 months now, and I don't want to go back! I care less about code
quality and more about easily adding animation and motion w/o writing code.
But, the better code this thing churns, the more support it will get from
the engineers I work with everyday.

You're absolutely right of course, that better tools do not mean better
designs, but those with good design chops and UCD skills could very rapidly
create a working prototype, do some usability testing, incorporate changes
based on the tests, then deliver a working prototype that can be used as a
starting point for engineers to write production level code. In my
situation, it would also cut down on the amount of storyboarding, activity
diagrams and use cases I need to spend time on. That's pretty powerful
(especially for anyone trying to make Agile + UCD play nice), and will lead
to higher quality designs in my opinion, as long as it's used by experienced
designers and UCD practitioners. It's what I wanted MS' Expression Blend
(right name?) to be. I'm really excited about the potential around products
like this, and I hope Adobe delivers. Soon.

On Tue, 2 Oct 2007 14:37:06, pauric <radiorental at gmail.com> wrote:
>
> For me, the killer feature for any designer orientated app in the
> toolchain is the ability to generate succinct legible code thats easy
> for a developer (or designer) to debug.
>
> >From the MacWorld article: "Designers using Thermo don%u2019t have
> to write code for their applications, but they can choose to view the
> source code and see it in a Flex Builder editor that they can work
> with if they want to"
>
> Making note of this ability a year out from release hints to me that
> this will be a key aspect of the app.
>
> Concern.. assuming there will be pattern libraries for such apps.
> This will enable more intuitive designers out of the closet but does
> not, nor should it, provide you with magic UCD skills. The same way
> anyone with a copy of Photoshop can make a digital photo look pretty
> and make them feel like a professional without having to read up on
> what it takes to take professional photos.
>

2 Oct 2007 - 5:01pm
dmitryn
2004

True. But "ability to generate source code that can be viewed in an
editor" and "ability to generate succinct legible code that's easy to
debug" are very different things.

I'd be (happily) surprised if Thermo can deliver the latter rather
than the former, especially in its first release.

Dmitry

On Tue, 2 Oct 2007 14:37:06, pauric <radiorental at gmail.com> wrote:
> For me, the killer feature for any designer orientated app in the
> toolchain is the ability to generate succinct legible code thats easy
> for a developer (or designer) to debug.
>
> >From the MacWorld article: "Designers using Thermo don%u2019t have
> to write code for their applications, but they can choose to view the
> source code and see it in a Flex Builder editor that they can work
> with if they want to"

2 Oct 2007 - 5:28pm
.pauric
2006

No doubt, my point is they're mentioning it a year out from release which
says to me its a 'feature' not a byproduct/afterthought. As such, its being
designed. So, yes.. its not going to be beautifully commented code,
conversely I doubt very much its going to be the illegible garbage something
like iWeb spews out.

The purpose of this tool is to connect designers and developers, whats the
point if developers cant hook in to the exports easily?

Syndicate content Get the feed