No device activation, no license returns, no lost licenses in crashed disks.Ī subscription model also means that we will take care of existing users with the same priority as new users because the monetary reward for a renewal is exactly the same as for a new user. This means that you can install Xbench on as many devices as you wish and simply sign in to use Xbench. With Xbench 3.0 we are introducing a flexible subscription model based on named users, where your email is the Xbench account you use for your license. However, in order to maintain a proper motivation for its development, this decision means that Xbench 3.0 will become a paid product. With this decision - and therefore without this restriction - we can now fully focus on making Xbench a great tool for even more users. We believe that this decision will greatly contribute to enhance the support of some formats whose functionality was not at par to other formats more important to ApSIC’s daily production. So with this release, we’ve made an important decision: we will no longer require that any change to ApSIC Xbench has to be fully symbiotic with ApSIC’s needs as an LSP. Indeed, the main feature of ApSIC Xbench 3.0, Unicode support, was probably something that we at ApSIC could get by without it because of the main language pairs we focus on. There were many user suggestions that, although they were useful for users in general, we were reluctant to implement because they were for a CAT tool that ApSIC did not like anymore (or did not like enough yet), or they were for needs that we had already covered in some other way, or they were needs that we simply didn’t have. However, as the Xbench user base grew, tensions on the feature set appeared. At the same time, external users benefit from using a great tool. External users provided very helpful feedback that allowed us to improve a tool that is essential for ApSIC own production processes as an LSP. And many other enhancements all over the placeįor many years, we’ve seen Xbench has been as a symbiotic product. ![]()
0 Comments
Leave a Reply. |