Maybe it is useful to answer the question "what is a portable app" first as it maybe different on PE and legacy Windows.
On regular Windows a portable app may be defined as following the same standards as set by portableapps.com :
an app does not write to registry or user-profiles and keeps all its configuration-files inside its own directory.
This way it can be stored on an external USB-disk and can be used on different systems. Plugin the USB-disk - browse to the directory and launch it.
In PE it doesn't matter that much if an app writes to the registry or the user profile so maybe we can keep the definition of "portable" wider than with regular Windows.
In PE we can also call apps "portable" when they copy files to X:\i386 or install drivers - maybe the only requirements are that
the app can be stored where-ever and does not need any special preparations during building of the PE.
In MOA I use the term "load on demand" - if an app can be loaded on demand after boot of the PE it is portable - if not - it requires a plugin or .script.
Obviously we also have to keep various dependancies in mind: an app maybe loaded on demand in MOA but may not work in a very naked native_XP.
Anyway - it would be useful for this section if we agree on some basics first - otherwise users maybe frustrated if a so called "portable apps" will not work on their build as dependancies are missing
![:cheers:](http://reboot.pro/public/style_emoticons/default/cheers.gif)
Ulli