Mac App Blocker

It’s true that Mac App Blocker can be disabled with this AppleScript. However, it seems that this method is certainly beyond the abilities of the “average” user.
This AppleScript uses the OS functionality at the lowest level to disable an app. It would be very inappropriate for any app developer to prevent operation of the OS at this level.

The criticism that Mac App Blocker is a memory hog with memory leaks is simply now true.
In the 5 years that Mac App Blocker has been available, it has NEVER overloaded a CPU to the point of making the computer unresponsive. We have NEVER heard from anyone that the app had caused a system lockup or even hinted at an issue with CPU usage.

The app is throughly tested on multiple computers with multiple OS versions before release. If this user is experiencing this issue, I would suggest looking elsewhere for potential culprits - because its NOT from Mac App Blocker.

Though, maybe I’m being too critical of this users review. After all, the app was just released yesterday and this user has already spent an exhaustive amount of time evaluating it - in the past 12 hours. (In addition to reviewing 8 other apps here on MacUpdate at the same time).

Why is it that whenever we release a new version, we receive a number of negative reviews - though competitive apps do not receive the same critiques. Even though the issues and faults of Mac App Blocker could easily apply to the other apps, they never receive these 1 star reviews.

As always - everybody is entitled to his/her own opinion. Some users may find Mac App Blocker useful and others may not. This is why we offer a 15 day trial period.

You should chill. Really, take my comments as a gift to improve your tool instead of saying my comments aren’t true. That is plain rude and doesn’t make you look any better. Respect to your customers is in place here.

The memory leaking is very true. Watching the Activity Monitor while adding a new app to protect results in about +5MB and removing it back again +5MB. Launching a protected app also leaks memory. I can imagine if it run for days without hard resetting a system, it can become a serious problem. I noticed this in the Activity Monitor because of the CPU peaking problems that I noticed before.

About CPU hungry. This is true too. Sometimes launching a protected app gives the rainbow pointer and CPU is peaking for long time until the unlock window is shown. This is random but it does happen here.

I tried your app in the past and had the same problems. I was hoping this new version fixed these problems. It does not. I do want to use MacAppBlocker for our children, but in it’s current state it is not good.

I tried alternatives like ILock but that app cannot handle time schemes and is very basic. Although it does work fine it is not my fit.

I call myself an average user with some knowledge about Apple Script and Automator because I use it daily. It is no rocket science.

I apologize for the web site contact page issue. We'll have it operating as soon as possible.
To answer your question - the user agreement states you can load Mac App Blocker on up to 3 computers within the same household.
If you have any other question, you can contact us at: support@knewsense.com

As I explained previously, if an application is running in OSX, you CANNOT remove, delete, or modify it in any way. OSX will not allow this (please see the response below to StevensPeter). Also, I'm not sure which version of Mac App Blocker you did your testing with, but the last few versions (since 10.5.3) have employed a package installer that sets the disk permission to only allow the admin to delete or modify. However, we do offer a 15 day trial period to test Mac App Blocker to ensure it meets the individual's needs. I encourage anyone to download and install Mac App Blocker (provide an admin password to install) and test Ollie1972's assessment that it can be easily removed without the admin password.

@KnewSense LLC that makes your app unnecessary. If you cannot use it safely with Admin right, you can better make a guest or user profile with restrictions. Thats the whole point of your app, protect application from running in Admin mode. and for what its worth: yes, you cannot remove the app with dragging it to the trash, however removing it with any uninstaller (iTrash worked for me) is indeed possible while it is running. No admin password was asked in my successful attempt. There seems to be another similar app named ILock and that refuses to be removed even with an uninstaller, making that simple alternative app safer to use. That said, ILock is still in beta which isn't a good idea to use in production.

I am perplexed by this scenario. I have tested this on multiple systems using a variety of settings and have not experienced this behavior when uninstalling the app. It ALWAYS asks for the admin password. The only thing I could do to come close to duplicating what is described here is to set my admin password to nothing (not recommended). I was still prompted to enter my password, but could just hit OK in response.

Confirming this. Uninstall this with Appdelete without asking for any password, reboot your system and gone is the protection. For first line protection - read: Users that do not know the insides of OS X, it can be useful. A more experienced users bypasses this with ease. The asking fee is too high for such low protection. A price of about $10 would be more advisable.