Home

Services

Product design
Rapid Prototypes

CNC prototypes
Rapid Prototyping
Stereolithography Apparatus (SLA)
Selective Laser Sintering (SLS)
Fused Deposition Modeling (FDM)
Laminated Object Manufacturing (LOM)

Custom molds - plastic molds

Injection molds
Blow molds
Compression molds
Extrusion molds
Other custom molds

Plastic molding

Injection molding
Blow molding
Compression molding
Extrusion Molding

Production tooling

Portfolio

Successful Products

Electronic Products
Home Appliances
Sports Accessories

Rapid Prototyping Prototypes

SLA Prototypes
CNC Prototypes
LOM Prototypes
SLS Prototypes
FDM Prototypes

Custom molds - Plastic molds

Injection molds
Blow Molds
Compression Molds
Extrusion Molds
Other Custom Molds

Workflow

Communication Requirements
Product Design contract

Appearance Design
Configuration Design

Rapid prototyping prototype Creation
Custom molds
Production tooling - manufacturing

8. Rapid Prototyping Discussion

Rapid Prototyping is a great way to develop new ideas quickly and accurately. I use rapid prototyping all the time if it be in AS3 or Javascript, a game or an application. Whilst game and application development are very different, the same rapid prototyping methods can be applied.

Lets examine a few points from the following aspects:

"Embrace the Possibility of Failure - it Encourages Creative Risk Taking"
This is the most crucial concept to grasp when rapid prototyping. Before i had a rather cautious view on development, i would constantly be thinking "I could also do it this way but i better do it the way i've seen before" when actually if i had prototyped a few examples i would probably have developed the end product faster and it would probably be more efficient.

"Simulate in Your Head - Pre-Prototype the Prototype"
Many developers will be thinking "Duh of course" every developer has an idea of how to develop an idea programatically. But the key here is to not limit yourself entirely to how your application or game will work, but to think of it as a whole, interface, animations, graphics and usability. I've applied this approach to Wuup's AIR apps (which were rapid prototypes though with extra polish :P) Which was the first time i applied the prototyping technique. They both took approx and hour to think of and deploy.

"Build the Toy First"
This is my favorite point, because i write a lot of experimental apps and i've always built the fun part first. The reason you develop the toy first is that, if you dont, you might end up with a great UI, animation and efficiency but the main function of your application could be flawed ("You Can't Polish a Turd" as they say).

"Build Toward a Well Defined Goal"
Many of you who have developed large applications know how important this statement is. You can work as long as you like o a project but without well defined goals your work could prove ultimately pointless.

Rapid prototyping isn't entirely a solitary experience, two programmers working very well together can achieve much in a short space of time. Both me and Alan have prototyped several pieces of software to much success. Though be prepared for many arguments about how things should and shouldn't be done.

In closing, rapid prototyping can be your friend if you are of the right mindset. But be prepared for failure and never spend too long on a prototype.