Zugg Software :: FAQ

Frequently Asked Questions

If I write a program using zApp, do my users need to buy zApp too?: No. Using the zApp Pro IDE you can encrypt your zApp program, then link it into an EXE, and then just distribute the EXE to your customers. The EXE will be about 4-5MB in size and will contain everything your customer needs to run your application. When the customer runs the EXE file, your encrypted ZXL zApp file will be automatically extracted to their hard disk. So, to send updates of your software to your customers, you only need to distribute the very small encrypted ZXL files.
How do my users customize my application?: In order to customize your application, the end-user must purchase their own copy of zApp. Regardless of whether you distribute the full ZML text source to your application, or whether you just distribute the encrypted ZXL file, customers with the full version of zApp can still write plugins, or add their own features to your program, without disturbing your protected code.
How protected is my application code?: When your application is encrypted using the zApp Pro IDE, strong 128 bit RSA encryption is used. There is no way for a normal user to break this encryption, so they cannot modify your application. However, since much of your application uses the Microsoft Scripting Engine, it is possible for advanced users to use Microsoft Debugger tools to see your application scripts as they are run. While these encrypted scripts cannot be changed, you should not store passwords or other sensitive data in your scripts. While users with a full version of zApp can add plugins and customize your application, there is no way for them to overwrite your scripts or directly change your application logic. Only if you distribute the full text ZML source code for some of your modules could users completely change the program logic. This system provides the best of both worlds: the ability for users to customize and write plugins, while protecting your own sensitive code.
What version of zApp do I need?: If you are a developer who wants to write programs in zApp and then distribute these programs to other users, then you need both the regular registered version of zApp (the zApp end-user edition), and the zApp Pro IDE. The zApp Pro IDE is used to encrypt and link your zApp programs so they can be distributed to other users.; If you just want to customize an existing zApp program or write a plugin for an existing program, then you just need the regular version of zApp (the zApp end-user edition). You don't need the zApp Pro IDE unless you want to distribute your program or plugins.; If you just want to run an encrypted or linked zApp program and don't want to customize it, then you just need the free zAppLite version, which is usually bundled with the application by the developer.
Can I sell my own zApp programs?: Yes. There are no royalties for any program created using zApp. We are working on an arrangement with eLicense that would allow you to sell and market your program via eLicense and Zugg Software without needing your own merchant account or eCommerce system. Details on this arrangement are still being worked out. Of course, you are highly encouraged to promote the full version of zApp to your customers so that they can customize your application and write their own plugins.
Why should I use zApp instead of XXX (fill in the blank)?: See the section on Comparison between zApp and other application development systems. There are Pros and Cons for every development tool. zApp provides a fully functional 30-day free trial of all its products so that you can use the tools and see if they meet your needs before buying them.
Is Source Code for zApp available?: Yes and No. Much of zApp, such as the zApp Pro IDE, and the zApp Documentation Viewer, are written in zApp, and most of the source code for these programs are available. However, source code for the core parts of zApp itself are not available. See the Contributions article for a list of 3rd party components used in zApp.
Is there a manual for zApp?: No hardcopy manual is currently available. zApp is being improved on a daily basis, and traditional paper manuals just can't keep up and would be out-of-date as soon as they were published. A full online manual is available in the zApp Reference Area. This information is also available via the zApp Documentation Viewer program that comes with the zApp Pro IDE. This Documentation Viewer is written in zApp itself (and comes with full source code), and can download documentation updates from this web site for offline viewing and searching.

: Mon Nov 06, 2006 5:45 am

: Mon Jan 22, 2007 7:51 pm

The key phrase is "normal user". Advanced hackers can certainly break the encryption, or just load the application into memory (where it is decrypted) and hook into the Microsoft Scripting engine to extract the source code. As it says in several locations, the encryption in zApp is not intended to be foolproof (there is no way to make it unbreakable with the simple technology being used in zApp). This is just like any other form of copy protection...there is really no way to stop hackers no matter what you do. But the encryption in zApp will prevent normal users from modifying your application. You certainly should not try to use it to protect valuable proprietary information. You shouldn't expect that sort of security from a <$50 development environment.