Hi all!!

I would like to design a customization site like the foolowing:

or

https://www.trekbikes.com/us/en/projectone/

but I have no idea of how to even begin. :icon_confused:

What should I use Flash or Flex?
How it works?
Is the customization done by changing any values in something like an XML file?

Can somebody give me any hints or even point me to some tutorials or information sources where I can learn how to create something like that?

Any help is appreciated :icon_idea:

Dani AI

Generated

Think of a customizer as a small production line rather than a single tool: an asset pipeline (how designer files are sliced and named), a realtime composition layer (how choices map to visible layers and transforms), a UI that guides selection and previews changes, a persistence layer for saves/permalinks/cart items, and a server-side export step that produces print-ready files and SKUs. Break the work into those pieces and design the data model that links UI choices to asset IDs and transforms. As and are already discovering, this is about process more than one language or IDE; and as warned, it’s not a tiny one-person job if you try to build everything at once.

Practical starting path: prototype the interaction with static images or a simple web mock to lock UX before coding. Define a strict naming convention for assets and a minimal JSON model that maps option keys to layer visibility, color transforms, and texture overlays. Implement the minimum viable features first β€” color swaps, component toggles, one decal layer, save/load β€” then add uploads, pricing rules, and shareable links. Serve assets efficiently (sprite sheets, lazy load, vector where appropriate) and keep your render pipeline and server export using the same canonical assets so previews match production output.

Important note for anyone reading this long after the original thread: the browser/plugin landscape changed β€” the Flash plugin has reached end of life and major browsers no longer support it. For new work choose modern web standards (Canvas/SVG/WebGL) and a server export pipeline rather than relying on a deprecated plugin. ()

Next steps: document the product rules (allowed combos, pricing), make a tiny authoring tool so designers export consistent assets, then iterate the composer and export. If you inherit an old plugin-based customizer, treat migration as an asset-and-model port: keep the business rules and assets, but reimplement rendering with modern web tech so maintenance and browser compatibility are sustainable.

Recommended Answers

All 5 Replies

Member Avatar for Member #334542

Yes all these things should happen with Flash, AS2.0/AS3.0 Script, Animation, XML (as a simple database), PHP & SQL to use complex database and JavaScript.

Hi rajarajan07!

Thank you for your hint, it helped me to narrow down the problem just to flash :)

And do you know about any tutorial/s where I can find a solution for a similar design or where I can learn how to combine all of that things with flash?

Well, before coming here for answers I already tried that approach.
Because my knowledge and experience with flash is not that much I really need something more specific and related to this case.

Hope I can get information or a link to some tutorial that show how to create something similar to what I would like to create. :icon_rolleyes:

Thanks :)

You're after a complex answer which nobody will be able to answer for you. Nike site is not built by an amateur and incorporates many professional aspects of design/coding.

To start off Flash tutorials are your friend. Once you get Flash mastered then move onto the more advanced features.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.