Prototyping tools for mobile game app. (Wendy Fischer)

1 Nov 2006 - 3:05pm
1198 reads
Bob Lewis
2006

Wendy wrote:
>> I need something that 1) has a low learning curve, 2) is easy to port to
>a mass market phone and 3) utilizes a WYSIWYG interfaces without a lot of
>coding.
>> I'm not finding a lot. WAP isn't going to do it for me and Flash Lite
>seems like its available on a limited number of handsets, which tend also to
>be smartphones.
>> Any ideas, I'm stumped.
>> -Wendy

Have you looked into using Dreamweaver?

Others to look into are: Axure(http://www.axure.com) and ConceptDraw WebWave (http://www.conceptdraw.com/en/products/webwave/main.php)

Good Luck!
Robert Lewis

-----Original Message-----
>From: discuss-request at lists.interactiondesigners.com
>Sent: Nov 1, 2006 2:06 AM
>To: discuss at lists.interactiondesigners.com
>Subject: discuss Digest, Vol 37, Issue 30
>
>Send discuss mailing list submissions to
> discuss at lists.interactiondesigners.com
>
>To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.interactiondesigners.com/listinfo.cgi/discuss-interactiondesigners.com
>
>or, via email, send a message with subject or body 'help' to
> discuss-request at lists.interactiondesigners.com
>
>You can reach the person managing the list at
> discuss-owner at lists.interactiondesigners.com
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of discuss digest..."
>
>
>[For those using lower bandwidth, or the DIGEST version of this list; the administrators ask people to voluntarily trim their postings to only include relevant quoted material.]
>
>
>
>Today's Topics:
>
> 1. Re: error treatments (Michael Micheletti)
> 2. Re: Marking required fields on desktop UIs? (Daniel Szuc)
> 3. Re: Usability Labs on Hire :: India / USA (Shalini)
> 4. Re: Marking required fields on desktop UIs? (Alan Wexelblat)
> 5. Making Life Easy (and the Red Balloons) (Paul Adams)
> 6. Give-A-Little-Back-06 Final Tally (Gregory Petroff)
> 7. Re: error treatments (Robert Hoekman, Jr.)
> 8. Re: Marking required fields on desktop UIs? (Barbara Ballard)
> 9. Re: Marking required fields on desktop UIs? (Mark Canlas)
> 10. Re: Marking required fields on desktop UIs? (Alan Wexelblat)
> 11. Prototyping tools for mobile game app. (Wendy Fischer)
> 12. Re: Prototyping tools for mobile game app. (Jacco Nieuwland)
> 13. Re: Prototyping tools for mobile game app. (Barbara Ballard)
> 14. Re: Prototyping tools for mobile game app. (Wendy Fischer)
> 15. Re: email address as username (jackbellis.com)
> 16. Re: Prototyping tools for mobile game app. (Wendy Fischer)
> 17. Classes from Cooper (Valerie Gomez de la Torre)
> 18. Re: Classes from Cooper (Renato Almeida)
> 19. Re: Classes from Cooper (Chris Hallenbeck)
> 20. Re: "Interface-Free" Interface (Christian Sosa-Lanz)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Tue, 31 Oct 2006 02:06:56 -0800
>From: "Michael Micheletti" <michael.micheletti at gmail.com>
>Subject: Re: [IxDA Discuss] error treatments
>To: afischer at eemedia.com
>Cc: Interaction Designers
> <discuss-interactiondesigners.com at lists.interactiondesigners.com>
>Message-ID:
> <5eb0ab240610310206p66eb4098r8cb4fd9f7f41631b at mail.gmail.com>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>You might also want to take a look at the book "Defensive Design for the
>Web" from 37 Signals:
>
>http://www.amazon.com/Defensive-Design-Web-improve-messages/dp/073571410X
>
>The book discusses error messaging for web applications at some length.
>
>Michael Micheletti
>
>On 10/30/06, Anastasia Fischer <afischer at eemedia.com> wrote:
>>
>> [Please voluntarily trim replies to include only relevant quoted
>> material.]
>>
>> I am looking for examples of error treatments for web apps. Is there a
>> best-in-class standard for this these days?
>>
>>
>
>
>------------------------------
>
>Message: 2
>Date: Tue, 31 Oct 2006 18:51:44 +0800
>From: "Daniel Szuc" <dszuc at apogeehk.com>
>Subject: Re: [IxDA Discuss] Marking required fields on desktop UIs?
>To: <discuss-interactiondesigners.com at lists.interactiondesigners.com>
>Message-ID: <00ca01c6fcda$8f181cb0$e201470a at gamellian2>
>Content-Type: text/plain; charset="US-ASCII"
>
>Hi Alex:
>
>Perhaps not a standard but *changing the background colour of the field*
>that is mandatory. For example, yellow. This paired with the use of an
>asterix may work well.
>
>This may also be useful:
>http://www.formsthatwork.com/questionsanswers/asterisk.asp
>
>Rgds,
>
>Daniel Szuc
>Principal Usability Consultant
>Apogee Usability Asia Ltd
>www.apogeehk.com
>'Usability in Asia'
>
>-----Original Message-----
>From: discuss-bounces at lists.interactiondesigners.com
>[mailto:discuss-bounces at lists.interactiondesigners.com] On Behalf Of Alan
>Wexelblat
>Sent: Tuesday, October 31, 2006 7:15 AM
>To: discuss-interactiondesigners.com at lists.interactiondesigners.com
>Subject: [IxDA Discuss] Marking required fields on desktop UIs?
>
>
>[Please voluntarily trim replies to include only relevant quoted material.]
>
>Greetings
>
>I am having trouble determining if there is a standard or best practice for
>marking which fields are required on a desktop application form. This is a
>fairly standard Windows UI with lots of dialogs. Each dialog has some
>mandatory and some optional fields, and which are which tends to change with
>the data, system parameters, etc.
>
>Therefore, I want to have some visual treatment so users can know at a
>glance what fields are mandatory. On the Web there is a convention to mark
>required fields with asterisks (*) but this convention does not seem to have
>been back-ported to desktop UIs.
>
>Anyone have any pointers or suggestions?
>
>--
>--Alan Wexelblat
>________________________________________________________________
>Welcome to the Interaction Design Association (IxDA)!
>To post to this list ....... discuss at ixda.org
>List Guidelines ............ http://listguide.ixda.org/
>List Help .................. http://listhelp.ixda.org/ (Un)Subscription
>Options ... http://subscription-options.ixda.org/
>Announcements List ......... http://subscribe-announce.ixda.org/
>Questions .................. lists at ixda.org
>Home ....................... http://ixda.org/
>Resource Library ........... http://resources.ixda.org
>
>
>
>------------------------------
>
>Message: 3
>Date: Tue, 31 Oct 2006 17:12:24 +0530
>From: Shalini <shalini at u-dec.com>
>Subject: Re: [IxDA Discuss] Usability Labs on Hire :: India / USA
>To: <discuss at ixda.org>
>Message-ID: <000001c6fce1$a5ae9100$0f00a8c0 at UDEC.COM>
>Content-Type: text/plain; charset=us-ascii
>
>Hi Vikram,
>
>Check out http://www.humanfactors.com/services/usability-consulting.asp
>
>Shalini
>
>
>
>-------------------------------------------------------------------
>Uttaranchal Infrastructure Development Company Ltd, Dehradun, India
>
>
>------------------------------
>
>Message: 4
>Date: Tue, 31 Oct 2006 09:29:04 -0500
>From: "Alan Wexelblat" <awexelblat at gmail.com>
>Subject: Re: [IxDA Discuss] Marking required fields on desktop UIs?
>To: "Daniel Szuc" <dszuc at apogeehk.com>
>Cc: discuss-interactiondesigners.com at lists.interactiondesigners.com
>Message-ID:
> <d426917e0610310629r2225ba84oe58da82da6deda52 at mail.gmail.com>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>Yeah, I've been trying to avoid using a marking that is purely color,
>based on the fact that color isn't a great primary cue.
>
>As we're on the Windows desktop we also have to contend with the
>variety of "themes" that Windows permits users to layer over
>application UIs. It's not clear from the development desk that a
>color change would even be visible on some users' desktops.
>
>Thanks for the pointer - that appears to be a Web-oriented answer. I
>think the convention on the Web is pretty clear.
>
>--Alan
>
>On 10/31/06, Daniel Szuc <dszuc at apogeehk.com> wrote:
>>
>> Hi Alex:
>>
>> Perhaps not a standard but *changing the background colour of the field*
>> that is mandatory. For example, yellow. This paired with the use of an
>> asterix may work well.
>>
>> This may also be useful:
>> http://www.formsthatwork.com/questionsanswers/asterisk.asp
>>
>> Rgds,
>>
>> Daniel Szuc
>> Principal Usability Consultant
>> Apogee Usability Asia Ltd
>> www.apogeehk.com
>> 'Usability in Asia'
>
>
>------------------------------
>
>Message: 5
>Date: Tue, 31 Oct 2006 14:53:14 -0000
>From: "Paul Adams" <paul at flow-interactive.com>
>Subject: [IxDA Discuss] Making Life Easy (and the Red Balloons)
>To: <discuss-interactiondesigners.com at lists.interactiondesigners.com>
>Message-ID: <20061031145324.898EC1BB9A at che.dreamhost.com>
>Content-Type: text/plain; charset="us-ascii"
>
>Hi folks,
>
>
>
>I want to tell you about a project for World Usability Day called *Making
>Life Easy*. And I'm hoping that you will stop by and let us know your
>thoughts about good and bad design!
>
>
>
>*What is it?*
>
>
>
>Between now and World Usability Day (14th Nov), we'll be out on the streets
>of London tying red balloons to examples of good and bad user experiences.
>
>
>
>We've set up a blog http://www.makinglifeeasy.org/ and a Flickr group
>http://www.flickr.com/groups/makinglifeeasy/.
>
>
>
>We're documenting examples of good and bad design on the blog, and in the
>case of the latter, providing solutions to how it could be better.
>
>
>
>The aim is to:
>
>- Raise awareness to business about the needlessly bad experiences they
>create for their customers. And where appropriate, show how they might be
>able to create a better experience.
>
>- Raise awareness amongst the public about how design impacts on their
>lives.
>
>
>
>We'll be collecting votes for the Usability Hall of Shame and the Usability
>Hall of Fame. We'd LOVE you to get involved.
>
>
>
>Participants are encouraged to photograph good and bad user experiences and
>either:
>
>- add it to our Flickr group http://www.flickr.com/groups/makinglifeeasy/
>
>- email it to us (hello [at] makinglifeeasy.org) and we'll post it to the
>website
>
>
>
>There are a few other things you could do to help:
>
>
>
>1. Help get more people involved! If you have a blog, give us a shout out
>and send people our way to participate. If you have a Flickr account, come
>join our group and invite all your friends!
>
>
>
>2. Share your examples of the best and the worst user experiences where you
>live (or visit, or holiday). Add photos to the Flickr group, or drop us an
>email and we'll add your submission to the website and potentially to the
>Hall of Fame or Shame
>
>
>
>3. Cast your vote! Take a look at the website and have your say in what
>*really* drives you crazy and what you really love.
>
>
>
>Thanks for listening,
>
>
>
>Let us know your thoughts!
>
>
>
>Paul.
>
>
>
>
>
>------------------------------------------------
>
>
>
>Paul Adams :: User Experience Consultant
>
>
>
>Flow Interactive Ltd
>
>
>
>t: +44 (0)20 7288 0884
>
>f: +44 (0)20 7690 1090
>
>
>
>e: paul at flow-interactive.com
>
>
>
>See our website ... www.flow-interactive.com
>
>
>
>Paul's blog: <http://www.re-frame.info/blog> www.re-frame.info/blog
>
>
>
>------------------------------------------------
>
>
>
>This e-mail is for the use of the intended recipient(s) only. If you have
>received this email in error, please notify the sender immediately and then
>delete it. If you are not the intended recipient, you must not read, use,
>disclose or distribute this e-mail without the author's prior permission.
>
>
>
>
>
>------------------------------
>
>Message: 6
>Date: Tue, 31 Oct 2006 08:01:14 -0800
>From: "Gregory Petroff" <greg.petroff at gmail.com>
>Subject: [IxDA Discuss] Give-A-Little-Back-06 Final Tally
>To: ixda <discuss at ixda.org>
>Message-ID:
> <4d84276c0610310801m82cc42cpeffca7c172b7ac7c at mail.gmail.com>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>Hi All,
>
>Thanks to all who contributed last week for our first fundraising campaign!
>
>We raised $3401.00. We ended up short of our goal of raising $5000, but we
>came close.
>
>Special thanks also to our generous challenge grant providers:
>
>Robert Reinnman
>Josh Seiden
>Lada Gorlenko
>Kim Goodwin with Cooper's very generous challenge grant.
>
>And another thank you to Jared Spool from UIE who made a sizable
>contribution to the effort.
>
>
>With your support we will be able to create a better experience for all of
>us in IxDA.
>
>--Greg Petroff
>Treasurer and Board Member IxDA
>
>
>------------------------------
>
>Message: 7
>Date: Tue, 31 Oct 2006 09:16:27 -0700
>From: "Robert Hoekman, Jr." <rhoekmanjr at gmail.com>
>Subject: Re: [IxDA Discuss] error treatments
>To: "Michael Micheletti" <michael.micheletti at gmail.com>
>Cc: Interaction Designers
> <discuss-interactiondesigners.com at lists.interactiondesigners.com>,
> afischer at eemedia.com
>Message-ID:
> <93e5ba540610310816t5e73fe78y65045503e3257632 at mail.gmail.com>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>Good point - that was a great book. Obvious stuff, but obvious in that way
>where it's good to keep it on your shelf as a reminder.
>
>-r-
>
>On 10/31/06, Michael Micheletti <michael.micheletti at gmail.com> wrote:
>>
>> [Please voluntarily trim replies to include only relevant quoted
>> material.]
>>
>> You might also want to take a look at the book "Defensive Design for the
>> Web" from 37 Signals:
>>
>> http://www.amazon.com/Defensive-Design-Web-improve-messages/dp/073571410X
>>
>> The book discusses error messaging for web applications at some length.
>>
>> Michael Micheletti
>>
>> On 10/30/06, Anastasia Fischer <afischer at eemedia.com> wrote:
>> >
>> > [Please voluntarily trim replies to include only relevant quoted
>> > material.]
>> >
>> > I am looking for examples of error treatments for web apps. Is there a
>> > best-in-class standard for this these days?
>> >
>> >
>> ________________________________________________________________
>> Welcome to the Interaction Design Association (IxDA)!
>> To post to this list ....... discuss at ixda.org
>> List Guidelines ............ http://listguide.ixda.org/
>> List Help .................. http://listhelp.ixda.org/
>> (Un)Subscription Options ... http://subscription-options.ixda.org/
>> Announcements List ......... http://subscribe-announce.ixda.org/
>> Questions .................. lists at ixda.org
>> Home ....................... http://ixda.org/
>> Resource Library ........... http://resources.ixda.org
>>
>
>
>------------------------------
>
>Message: 8
>Date: Tue, 31 Oct 2006 10:44:47 -0600
>From: "Barbara Ballard" <barbara at littlespringsdesign.com>
>Subject: Re: [IxDA Discuss] Marking required fields on desktop UIs?
>To: "Alan Wexelblat" <awexelblat at gmail.com>
>Cc: discuss-interactiondesigners.com at lists.interactiondesigners.com
>Message-ID:
> <d537ddd20610310844k61898a9flbe4b5033d0faf75c at mail.gmail.com>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>I find this question so very interesting because I recall, back in
>1996 or so, doing Windows design and having required fields marked
>with asterisks.
>
>On 10/30/06, Alan Wexelblat <awexelblat at gmail.com> wrote:
>>
>> Therefore, I want to have some visual treatment so users can know at a
>> glance what fields are mandatory. On the Web there is a convention to
>> mark required fields with asterisks (*) but this convention does not
>> seem to have been back-ported to desktop UIs.
>>
>
>--
>Barbara Ballard
>barbara at littlespringsdesign.com 1-785-550-3650
>
>
>------------------------------
>
>Message: 9
>Date: Tue, 31 Oct 2006 11:58:56 -0500
>From: "Mark Canlas" <mark at htmlism.com>
>Subject: Re: [IxDA Discuss] Marking required fields on desktop UIs?
>To: "'Alan Wexelblat'" <awexelblat at gmail.com>,
> <discuss-interactiondesigners.com at lists.interactiondesigners.com>
>Message-ID: <000601c6fd0d$dfa0b010$0501a8c0 at GENERALTSO>
>Content-Type: text/plain; charset="us-ascii"
>
>Sure, I can think of one. It's more behavioral than visual though...
>Mandatory fields that need to be filled out just won't let you proceed to
>the next screen. If you try to continue (like pressing enter on the password
>screen without giving a password), that yellow tooltip/balloon pops up (with
>an auditory warning), reminding you that a password is necessary. Also, for
>wizards, the next button is usually grayed out until all of the required
>text fields have something in them. Type at least one letter/number, then
>the button un-disables itself.
>
>-Mark
>
>> I am having trouble determining if there is a standard or best
>> practice for marking which fields are required on a desktop
>> application form. This is a fairly standard Windows UI with lots of
>> dialogs. Each dialog has some mandatory and some optional fields, and
>> which are which tends to change with the data, system parameters, etc.
>>
>> Therefore, I want to have some visual treatment so users can know at a
>> glance what fields are mandatory. On the Web there is a convention to
>> mark required fields with asterisks (*) but this convention does not
>> seem to have been back-ported to desktop UIs.
>
>
>
>------------------------------
>
>Message: 10
>Date: Tue, 31 Oct 2006 13:52:17 -0500
>From: "Alan Wexelblat" <awexelblat at gmail.com>
>Subject: Re: [IxDA Discuss] Marking required fields on desktop UIs?
>To: "Mark Canlas" <mark at htmlism.com>
>Cc: discuss-interactiondesigners.com at lists.interactiondesigners.com
>Message-ID:
> <d426917e0610311052vc40a7b7k6c9104e017464ac3 at mail.gmail.com>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>On 10/31/06, Mark Canlas <mark at htmlism.com> wrote:
>> Mandatory fields that need to be filled out just won't let you proceed to
>> the next screen. If you try to continue (like pressing enter on the password
>> screen without giving a password), that yellow tooltip/balloon pops up (with
>> an auditory warning), reminding you that a password is necessary. Also, for
>> wizards, the next button is usually grayed out until all of the required
>> text fields have something in them. Type at least one letter/number, then
>> the button un-disables itself.
>
>Yes, we already do these things. The problem is that the application
>contains a large number of forms, many of which have dozens of
>controls. I don't think it's a good usability plan to ask users to
>memorize or guess which fields then need to frob to make the "save"
>button light up.
>
>I agree that we ought not to let users save incomplete (and therefore
>error-producing) entries. But we need some kind of visual guide as
>well.
>
>--Alan
>
>
>------------------------------
>
>Message: 11
>Date: Tue, 31 Oct 2006 12:34:34 -0800 (PST)
>From: Wendy Fischer <erpdesigner at yahoo.com>
>Subject: [IxDA Discuss] Prototyping tools for mobile game app.
>To: discuss at ixdg.org
>Message-ID: <20061031203434.83901.qmail at web37211.mail.mud.yahoo.com>
>Content-Type: text/plain; charset=iso-8859-1
>
>I am researching prototyping tools for mobile games that are developed in J2ME and Brew. I need to create rapid prototypes of interfaces relatively quickly and be able to port something to a mass market phone for a usability test or a marketing demo.
>
> I need something that 1) has a low learning curve, 2) is easy to port to a mass market phone and 3) utilizes a WYSIWYG interfaces without a lot of coding.
>
> I'm not finding a lot. WAP isn't going to do it for me and Flash Lite seems like its available on a limited number of handsets, which tend also to be smartphones.
>
> Any ideas, I'm stumped.
>
> -Wendy
>
>
>
>------------------------------
>
>Message: 12
>Date: Tue, 31 Oct 2006 22:23:11 +0100
>From: Jacco Nieuwland <jacco at nieuwland.net>
>Subject: Re: [IxDA Discuss] Prototyping tools for mobile game app.
>To: Wendy Fischer <erpdesigner at yahoo.com>
>Cc: discuss at ixdg.org
>Message-ID: <4547BEBF.9030700 at nieuwland.net>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>
>Hi Wendy,
>
>How interactive does your prototype need to be? I have previously
>created a mobile prototype with swipr, a plugin for Visio
>(www.swipr.com). It will generate a prototype based on images with
>imagemaps, so any phone with a browser that handles images, imagemaps
>and javascript will be able to view the prototype.
>
>It will NOT have any animated stuff in there, nor will it feature input
>fields, but for an early, mid-fi prototype I have found it satisfactory,
>as it does allow people to view the prototype on the mobile phone, and
>navigate through it.
>
>Let me know if you want to know more,
>
>Jacco Nieuwland
>
>
>
>
>
>
>------------------------------
>
>Message: 13
>Date: Tue, 31 Oct 2006 15:26:51 -0600
>From: "Barbara Ballard" <barbara at littlespringsdesign.com>
>Subject: Re: [IxDA Discuss] Prototyping tools for mobile game app.
>To: "Wendy Fischer" <erpdesigner at yahoo.com>
>Cc: discuss at ixdg.org
>Message-ID:
> <d537ddd20610311326v1a435df5j1371637cedf47ccd at mail.gmail.com>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>Wendy,
>
>Flash Lite gets you many Verizon phones as well, but I don't have a
>good list. BREW would get you all Verizon phones and some European
>phones. You can also try pure J2ME (Java Mobile), but in a "build
>environment" like J2ME Polish. This is used to remove some of the
>vagaries of deploying to multiple phones, and you can use high-level
>widgets and then style them with CSS. The game play itself would
>undoubtedly still be a Canvas, but this gets you much faster to
>market.
>
>On 10/31/06, Wendy Fischer <erpdesigner at yahoo.com> wrote:
>> [Please voluntarily trim replies to include only relevant quoted material.]
>>
>> I am researching prototyping tools for mobile games that are developed in J2ME and Brew. I need to create rapid prototypes of interfaces relatively quickly and be able to port something to a mass market phone for a usability test or a marketing demo.
>>
>> I need something that 1) has a low learning curve, 2) is easy to port to a mass market phone and 3) utilizes a WYSIWYG interfaces without a lot of coding.
>>
>> I'm not finding a lot. WAP isn't going to do it for me and Flash Lite seems like its available on a limited number of handsets, which tend also to be smartphones.
>>
>> Any ideas, I'm stumped.
>>
>> -Wendy
>>
>> ________________________________________________________________
>> Welcome to the Interaction Design Association (IxDA)!
>> To post to this list ....... discuss at ixda.org
>> List Guidelines ............ http://listguide.ixda.org/
>> List Help .................. http://listhelp.ixda.org/
>> (Un)Subscription Options ... http://subscription-options.ixda.org/
>> Announcements List ......... http://subscribe-announce.ixda.org/
>> Questions .................. lists at ixda.org
>> Home ....................... http://ixda.org/
>> Resource Library ........... http://resources.ixda.org
>>
>
>
>--
>Barbara Ballard
>barbara at littlespringsdesign.com 1-785-550-3650
>
>
>------------------------------
>
>Message: 14
>Date: Tue, 31 Oct 2006 13:47:36 -0800 (PST)
>From: Wendy Fischer <erpdesigner at yahoo.com>
>Subject: Re: [IxDA Discuss] Prototyping tools for mobile game app.
>To: Barbara Ballard <barbara at littlespringsdesign.com>
>Cc: discuss at ixdg.org
>Message-ID: <20061031214736.70970.qmail at web37204.mail.mud.yahoo.com>
>Content-Type: text/plain; charset=iso-8859-1
>
>I'm just looking for something simple to 1) Create functional interactive prototypes, 2) create demos for marketing and 3) create throw away prototypes for usability testing. All this will be strictly UI, no backend. I'm not really worried about multiple phone support, I'll probably just choose our most commonly used phone and go with that.
>
>I'll take a look at J2ME polish, but I'm looking for something with a relatively low overhead on the coding. If I don't have to code at all that's what I'm looking for.
>
>Barbara Ballard <barbara at littlespringsdesign.com> wrote: Wendy,
>
>Flash Lite gets you many Verizon phones as well, but I don't have a
>good list. BREW would get you all Verizon phones and some European
>phones. You can also try pure J2ME (Java Mobile), but in a "build
>environment" like J2ME Polish. This is used to remove some of the
>vagaries of deploying to multiple phones, and you can use high-level
>widgets and then style them with CSS. The game play itself would
>undoubtedly still be a Canvas, but this gets you much faster to
>market.
>
>On 10/31/06, Wendy Fischer wrote:
>> [Please voluntarily trim replies to include only relevant quoted material.]
>>
>> I am researching prototyping tools for mobile games that are developed in J2ME and Brew. I need to create rapid prototypes of interfaces relatively quickly and be able to port something to a mass market phone for a usability test or a marketing demo.
>>
>> I need something that 1) has a low learning curve, 2) is easy to port to a mass market phone and 3) utilizes a WYSIWYG interfaces without a lot of coding.
>>
>> I'm not finding a lot. WAP isn't going to do it for me and Flash Lite seems like its available on a limited number of handsets, which tend also to be smartphones.
>>
>> Any ideas, I'm stumped.
>>
>> -Wendy
>>
>> ________________________________________________________________
>> Welcome to the Interaction Design Association (IxDA)!
>> To post to this list ....... discuss at ixda.org
>> List Guidelines ............ http://listguide.ixda.org/
>> List Help .................. http://listhelp.ixda.org/
>> (Un)Subscription Options ... http://subscription-options.ixda.org/
>> Announcements List ......... http://subscribe-announce.ixda.org/
>> Questions .................. lists at ixda.org
>> Home ....................... http://ixda.org/
>> Resource Library ........... http://resources.ixda.org
>>
>
>
>--
>Barbara Ballard
>barbara at littlespringsdesign.com 1-785-550-3650
>
>
>
>------------------------------
>
>Message: 15
>Date: Tue, 31 Oct 2006 16:48:18 -0500
>From: "jackbellis.com" <jackbellis at hotmail.com>
>Subject: Re: [IxDA Discuss] email address as username
>To: "discuss" <discuss at ixda.org>
>Message-ID: <BAY123-DAV9137EC26F25DA333961FAD1F90 at phx.gbl>
>Content-Type: text/plain; charset="iso-8859-1"
>
>Christina,
>
>I can see that some users have the "multiplicity" problem with email
>addresses and others have it with arbitrary names, and that determines which
>system one thinks is more flawed, irrespective of the anecdotal research.
>Perhaps if we were all told years ago to come up with bizarre usernames the
>problem wouldn't exist.
>
>I suspect that Robert's suggestion of making email addresses optional is
>heading us in the right direction, and if so, there might only be a couple
>of additional functional requirements to iron out. For instance, someone
>shouldn't be able to succeed in using an email address that belongs to
>another person. (This requires a verification bounce email, if that's the
>right term, if the login name is a viable email address.) The other
>requirement would seem to be disconnecting the login name from the internal,
>unique identifier, so users could change it even if they used an email
>address.
>
>Does Robert's suggestion work for you?
>Will PublicSquare allow @ and . in its login/user names, or is the
>question inapplicable?
>
>-Jack
>
>>>>>Robert Barlow-Busch:
>I believe that sites should not *require* an email address as the
>userID. It's common for some folks to have multiple addresses (which
>...
>--
>
>
>
>
>------------------------------
>
>Message: 16
>Date: Tue, 31 Oct 2006 13:56:13 -0800 (PST)
>From: Wendy Fischer <erpdesigner at yahoo.com>
>Subject: Re: [IxDA Discuss] Prototyping tools for mobile game app.
>To: discuss at ixdg.org
>Message-ID: <20061031215613.3833.qmail at web37202.mail.mud.yahoo.com>
>Content-Type: text/plain; charset=iso-8859-1
>
>I'm doing wireframes in Illustrator, but ideally I'd like to take the wireframes and put an interactive prototype together that can be deployed to the phone before we start writing design docs.
>
>I could probably go with Flash Lite, but the mobile footprint for Flash Lite still sucks. My company designs games for mass market phones (just Sprint right now), so I really want to be able to deploy and test on a mass market phone because that's what I have available.
>
>I'm gong to look at Polish and Ikivo. I will revisit Flash Lite but again, the device support was rather limited.
>
>jayhilwig <jayhilwig at cablespeed.com> wrote: Hi Wendy,
>
>I'm in a similar position of:
>-developing storyboards
>-developing prototypes for demo/marketing purposes
>-developing actual working (XML/javascript) code for carrier trials
>
>A number of people have looked at this problem in my company, and I don't
>see any clear path to go from prototype--->code without having dedicated
>developers create the code.
>
>Generally, storyboards are done in Visio. Demos done with a custom
>application (PHP) which creates javascript created with particulars to the
>device or OS(smartphones). Depending on the work requirements, I think
>FlashLite/photoshop will be used for prototyping.
>
>Disappointing, but not much different from win32 software development in my
>opinion. FWIW, I didn't find swipr (Visio thing) too helpful for mobile
>UI/IA. Flash/flash lite probably the best route if there is going to be
>coding anyway.
>
>Hope someone else has figured out a better route!
>_jay
>
>-----Original Message-----
>From: discuss-bounces at lists.interactiondesigners.com
>[mailto:discuss-bounces at lists.interactiondesigners.com] On Behalf Of Wendy
>Fischer
>Sent: Tuesday, October 31, 2006 1:48 PM
>To: Barbara Ballard
>Cc: discuss at ixdg.org
>Subject: Re: [IxDA Discuss] Prototyping tools for mobile game app.
>
>[Please voluntarily trim replies to include only relevant quoted material.]
>
>I'm just looking for something simple to 1) Create functional interactive
>prototypes, 2) create demos for marketing and 3) create throw away
>prototypes for usability testing. All this will be strictly UI, no backend.
>I'm not really worried about multiple phone support, I'll probably just
>choose our most commonly used phone and go with that.
>
>I'll take a look at J2ME polish, but I'm looking for something with a
>relatively low overhead on the coding. If I don't have to code at all
>that's what I'm looking for.
>
>Barbara Ballard wrote: Wendy,
>
>Flash Lite gets you many Verizon phones as well, but I don't have a
>good list. BREW would get you all Verizon phones and some European
>phones. You can also try pure J2ME (Java Mobile), but in a "build
>environment" like J2ME Polish. This is used to remove some of the
>vagaries of deploying to multiple phones, and you can use high-level
>widgets and then style them with CSS. The game play itself would
>undoubtedly still be a Canvas, but this gets you much faster to
>market.
>
>On 10/31/06, Wendy Fischer wrote:
>> [Please voluntarily trim replies to include only relevant quoted
>material.]
>>
>> I am researching prototyping tools for mobile games that are developed in
>J2ME and Brew. I need to create rapid prototypes of interfaces relatively
>quickly and be able to port something to a mass market phone for a usability
>test or a marketing demo.
>>
>> I need something that 1) has a low learning curve, 2) is easy to port to
>a mass market phone and 3) utilizes a WYSIWYG interfaces without a lot of
>coding.
>>
>> I'm not finding a lot. WAP isn't going to do it for me and Flash Lite
>seems like its available on a limited number of handsets, which tend also to
>be smartphones.
>>
>> Any ideas, I'm stumped.
>>
>> -Wendy
>>
>> ________________________________________________________________
>> Welcome to the Interaction Design Association (IxDA)!
>> To post to this list ....... discuss at ixda.org
>> List Guidelines ............ http://listguide.ixda.org/
>> List Help .................. http://listhelp.ixda.org/
>> (Un)Subscription Options ... http://subscription-options.ixda.org/
>> Announcements List ......... http://subscribe-announce.ixda.org/
>> Questions .................. lists at ixda.org
>> Home ....................... http://ixda.org/
>> Resource Library ........... http://resources.ixda.org
>>
>
>
>--
>Barbara Ballard
>barbara at littlespringsdesign.com 1-785-550-3650
>
>________________________________________________________________
>Welcome to the Interaction Design Association (IxDA)!
>To post to this list ....... discuss at ixda.org
>List Guidelines ............ http://listguide.ixda.org/
>List Help .................. http://listhelp.ixda.org/
>(Un)Subscription Options ... http://subscription-options.ixda.org/
>Announcements List ......... http://subscribe-announce.ixda.org/
>Questions .................. lists at ixda.org
>Home ....................... http://ixda.org/
>Resource Library ........... http://resources.ixda.org
>
>
>
>
>------------------------------
>
>Message: 17
>Date: Tue, 31 Oct 2006 15:51:17 -0600
>From: "Valerie Gomez de la Torre" <valeriegomez at gmail.com>
>Subject: [IxDA Discuss] Classes from Cooper
>To: discuss at ixdg.org
>Message-ID:
> <9ccd63010610311351v310afdd8ifed4179d640abcf2 at mail.gmail.com>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>Hello,
>
>Has anyone taken any of the classes offered by Cooper in San Francisco?
>
>Classes offered: http://www.cooper.com/content/cooperu/classes.asp
>
>Thanks!
>
>Valerie
>
>
>------------------------------
>
>Message: 18
>Date: Tue, 31 Oct 2006 17:49:04 -0500
>From: "Renato Almeida" <rfurno at gmail.com>
>Subject: Re: [IxDA Discuss] Classes from Cooper
>To: "Valerie Gomez de la Torre" <valeriegomez at gmail.com>
>Cc: discuss at ixdg.org
>Message-ID:
> <47cc6cc30610311449y26cc4210sc0e1dc6eaeb201a0 at mail.gmail.com>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>I took Interaction Design Practicum last year and it was really helpful (I
>am a Development Manager with no formal education on HCI or related
>disciplines, although I have strong technical background). I had previous
>contact with the work from Cooper and that made it much easier to understand
>the class topics and relate them to my actual work.
>
>The most important aspect of the class was the way it is explained because
>it made easy to tailor to the needs of the company I work for. This was
>specially important given that I needed buy-in from upper management in
>order to allocate *development* time for interaction design.
>
>Renato
>
>
>On 10/31/06, Valerie Gomez de la Torre <valeriegomez at gmail.com> wrote:
>>
>> [Please voluntarily trim replies to include only relevant quoted
>> material.]
>>
>> Hello,
>>
>> Has anyone taken any of the classes offered by Cooper in San Francisco?
>>
>> Classes offered: http://www.cooper.com/content/cooperu/classes.asp
>>
>> Thanks!
>>
>> Valerie
>> ________________________________________________________________
>> Welcome to the Interaction Design Association (IxDA)!
>> To post to this list ....... discuss at ixda.org
>> List Guidelines ............ http://listguide.ixda.org/
>> List Help .................. http://listhelp.ixda.org/
>> (Un)Subscription Options ... http://subscription-options.ixda.org/
>> Announcements List ......... http://subscribe-announce.ixda.org/
>> Questions .................. lists at ixda.org
>> Home ....................... http://ixda.org/
>> Resource Library ........... http://resources.ixda.org
>>
>
>
>------------------------------
>
>Message: 19
>Date: Tue, 31 Oct 2006 15:45:27 -0800
>From: "Chris Hallenbeck" <Chris.Hallenbeck at demandtec.com>
>Subject: Re: [IxDA Discuss] Classes from Cooper
>To: "Renato Almeida" <rfurno at gmail.com>, "Valerie Gomez de la Torre"
> <valeriegomez at gmail.com>
>Cc: discuss at ixdg.org
>Message-ID:
> <DEBD2137A3291A4AB7B2FFB5863A4F2D026E2AA9 at parrot.demandtec.com>
>Content-Type: text/plain; charset="us-ascii"
>
>
>
>I concur with this. I took the course and then had my whole team
>attend. I found we were able to able to immediately apply what we
>learned. There is no question that the software we designed was better
>for our target customers.
>
>
>Christopher D. Hallenbeck | Senior Director Product Management
>DemandTec, Inc. | 1 Circle Star Way, Suite 200 | San Carlos, CA 94070
>tel | + 1.650.226.4748 mob | + 1.415.341.3517 fax | +
>1.650.556.1190
>www.demandtec.com
>
>
>I took Interaction Design Practicum last year and it was really helpful
>(I
>am a Development Manager with no formal education on HCI or related
>disciplines, although I have strong technical background). I had
>previous
>contact with the work from Cooper and that made it much easier to
>understand
>the class topics and relate them to my actual work.
>
>The most important aspect of the class was the way it is explained
>because
>it made easy to tailor to the needs of the company I work for. This was
>specially important given that I needed buy-in from upper management in
>order to allocate *development* time for interaction design.
>
>**************************************************************************
>
>DemandTec Email Notice
>
>This email and any attachments may contain confidential and/or proprietary information and is intended solely for the use of the addressee. If you are not the intended recipient we request that you notify us via email or telephone and delete all copies of the message from your systems. Additionally, although DemandTec has taken reasonable precautions to ensure the security of this email and any attachments, we encourage you to take similar precautions and accept no liability for any loss or damage resulting from its use.
>DemandTec, 1 Circle Star Way, Suite 200, San Carlos, CA 94070, 650-226-4600
>
>
>------------------------------
>
>Message: 20
>Date: Tue, 31 Oct 2006 17:36:17 -0800
>From: Christian Sosa-Lanz <public at yellowmobile.com>
>Subject: Re: [IxDA Discuss] "Interface-Free" Interface
>To: ixda <discuss at ixda.org>
>Message-ID: <46A176E0-4270-4A10-81F6-EBA93905BBDF at yellowmobile.com>
>Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
>
>To Alain's point, I agree this is closer to a new product like the
>Palm Pilot and not just another thing to stick Windows and Office on.
>This type of product can open the doors for designers and others to
>return to a more manual or direct manipulation way of working. Car
>designer today still work on large paper, sitting flat on the desk
>and marker that they sweep around the page by moving , heaven forbid,
>their whole arm! Even through this isn't the most effective way of
>working, its the most direct, most creative medium. Sometimes its
>better to design the right thing slowly rather than the wrong thing
>quickly.
>
>This could lead to the return of dedicated products as opposed to the
>one for all MS Office approach which is less then desirable. Again
>bring the tie back to the Palm.
>
>The fatigue factor is something to consider, but moving your whole
>arm, standing, sitting means that you spread out repetition over many
>joints and easing the abuse on the old Carpel Tunnel.
>
>Other existing and new technologies can address feedback. Think
>rumble packs in joysticks and Apple's click wheel.
>
>Yeah I dreaming but there will eventually be a solution in this space.
>
>Christian Sosa-Lanz
>
>
>
>------------------------------
>
>________________________________________________________________
>Welcome to the Interaction Design Association (IxDA)!
>To post to this list ....... discuss at ixda.org
>List Guidelines ............ http://listguide.ixda.org/
>List Help .................. http://listhelp.ixda.org/
>(Un)Subscription Options ... http://subscription-options.ixda.org/
>Announcements List ......... http://subscribe-announce.ixda.org/
>Questions .................. lists at ixda.org
>Home ....................... http://ixda.org/
>Resource Library ........... http://resources.ixda.org
>
>End of discuss Digest, Vol 37, Issue 30
>***************************************

Syndicate content Get the feed