There is an intermediate layer of complexity between a RPM which offer a lot of features (full feature) at the cost of having to deal with its specific syntax (which is quite complex because it should deal with all the dependencies of the all the packages in the repository and with the installed ones) and executing shell scripts during a Patch Manager installation. Web Catalog is not the problem because it has to deal with a compressed archive (e.g. pippo.tar.gz) while the Patch Manager have just to execute 4 simple operations as far as all four scripts files exist. There is a HUGE gap between applying a patch (diff -pruN) and preparing a RPM, in this HUGE gap, Patch Manager shell scripting capability has its own place.
@olf - fulfilling that gap will step down the curve of people that can learn from doing a patch, doing a patch + scripting and the develop the skills to package an RPM. The learning curve should be as smooth as possible in order to enlarge the user-base and in this specific case the user-base means advanced smartphone users that get involved into modding / improving their system. If you expect that people jump from patching and packging, many will be lost. P.S.: BTW, hidden profile is not such a great sign of openess and trust towards the others people… 