# Nova App Build Task (for devs)

**URL:** <https://forums.realmacsoftware.com/t/nova-app-build-task-for-devs/52268>\
**Category:** Elements\
**Created:** [November 6, 2025, 2:17pm UTC](https://forums.realmacsoftware.com/t/nova-app-build-task-for-devs/52268 "2025-11-06T14:17:38Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![MultiThemes](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/multithemes/32/25117_2.png) [@MultiThemes](https://forums.realmacsoftware.com/u/MultiThemes)\
**Post date:** [November 9, 2025, 1:58pm UTC](https://forums.realmacsoftware.com/t/nova-app-build-task-for-devs/52268/16 "2025-11-09T13:58:07Z")

</div>

> [@Doobox](#):
>
> Thanks, but you will be able to add those as user groups in the app for repeated use on you’re projects.
> 
> What I need is exact replications of these core groups as found on most all of the core built in components

+1  
I’m working on it [thanks to](https://forums.realmacsoftware.com/t/multiple-choice-html-code/52266/2) @ben

Replicating a scenario similar to the basic options requires RMS to provide a complete HTML + JSON + Hooks example with all nested elements properly ordered.  
Despite my experience with stacks, the scenario is different, and in order to produce valid components to distribute in the store, developers should have access to the basic component structure.

This is also for consistency with the sales contract that RMS will propose for the new store. Users expect an equivalent level of quality, and we must satisfy them. 🙂

---

_[View the full topic](https://forums.realmacsoftware.com/t/nova-app-build-task-for-devs/52268)._