# Next steps
In the tutorial we covered the basic usage and functionality of the Roomle Web SDK in respect to the configurator. Now it's time to integrate the SDK into your project and workflow. Remember that the code in the example Code Sandbox is not intended for production use. Think how you can polyfil missing stuff for legacy browsers, how to efficently packaging your app etc.
In terms of the SDK check out our reference and start playing around with it. The best thing to learn is to try out.
# One note about SPAs
When you build a SPA (opens new window) it is common that DOM nodes are removed and added dynamically. You have two strategies to deal with this issue:
- add the canvas into a DOM node which is never remove and just show/hide this DOM node via CSS. This has the advantage that switching back and forth between the 3D scene and your app is very quick. On the other hand it could be a waste of memory and ressources if you always keep the 3D scene alive
pause()before the DOM node of the canvas is removed. Most of the modern UI frameworks give you the possibility to hook into some event which is fired before the DOM node is removed. When you navigate back to the page and want to show the canvas again you need to call
resume(). See our reference how to do this.
Nevertheless which strategy you choose you have to call
destroy() (for details see our reference) when you want to remove all the Roomle stuff completely.
# Final words
Report bugs and ask questions here http://servicedesk.roomle.com/ (opens new window)