Render Strategies¶
Platforme's tech stack provides 3 render strategies:
- PRC (Pre Render & Compose)
- SSR (Server Side Render)
- CSR (Client Side Render)
Each has its own Pros & Cons and appropriate Use Cases. As well as costs, artistic and technical requirements, file formats and associate runtime technology.
| Strategy | Pros | Cons | File Formats | Runtime Tech | Use cases |
|---|---|---|---|---|---|
| PRC | • Initial load time • Determinism • Simplicity (plain images) • Flexibility (pdp, emails, bag, etc.) • Ability to leverage photos | • Config change load time • Fixed resolution • Non-dynamic initials and patches • Composition visual limitations (eg: boundaries) | • PNG • JSON | P(NG) Convert | • Photography • Realism • Determinism • Low-cost pipeline |
| SSR | • Initial load time • Realism (ray-tracing et al.) • Simplicity (plain images) • Flexibility (pdp, emails, bag, etc.) • Dynamic initials and patches • Video capabilities | • Impact on infrastructure (running costs) • Bandwidth (framerate and resolution) • No dynamic animations • Requires new production pipeline | • FBX • SBSAR • PNG • HDR | Eevee Engine | • Realism • Dynamic resolutions • Dynamic initials and patches • Video animations |
| CSR | • Frame rate • Config change speed • Rotation around all axis • Dynamic initials and patches • Reduced infrastructure impact • Re-uses new production pipeline | • Slow initial load time • Lack of realism • Not flexible • Not portable (eg: Web != Native iOS) • Depends on client hardware | • FBX • glTF • PNG • HDR & EXR • JSON | Three.js Babylon.js | • Dynamic animation • Model exploring • Playing & gimmicking |