Resources can be configured to load client-side when specified entities are used.

<vaandroid>
    <!-- other stuff here ... -->
    <resources>
        <resource>
            <usedBy>activity</usedBy>
            <type>text/css</type>
            <path>/css/styles.css</path>
        </resource>
    </resources>
</vaandroid>

|| usedBy | plugin ~124~ activity ~124~ fragment ~124~ service | The entity that triggers the loading of the resource. If missing, ''plugin'' is used.%%%plugin - resource is loaded when the plugin is loaded.%%%activity - resource is loaded when the activity is launched%%%fragment - resource is loaded when the activity is used%%%service - resource is loaded when the service is activated

type | text/css ~124~ text/javascript | The mime-type of the resource. If missing, the type is infered from the resource name's extension

source | <<id>> | The owner of the resource. Currently, only plugins and bundles are supported. Specify the plugin or bundle id. If missing, the current plugin is used as the source.

path <<relative path>> The public resource path relative to the root of the bundle. For example, ''/css/styles.css'' in bundle mybundle would resolve to https://server.com/bundle/mybundle/css/styles.css
todo: allow soure to be a url
todo: specify usedBy entity by pattern
todo: implement fragment, and service
todo: implement javascript loader