FAQ

LIAPP is a mobile app security solution that protects Android and iOS mobile apps from a wide range of security threats such as reverse engineering, tampering, debugging, hooking, and rooting/jailbreaking. It protects the app's source code and runtime environment, and provides RASP features that detect and block threats while the app is running.

Mobile app security means protecting an app's source code, data, and runtime environment from a variety of attacks such as reverse engineering, tampering, and data theft. LIAPP applies a range of security features to the app so that it is protected not only during development but also in real user environments.

If a mobile app is attacked, it can lead to leakage of source code and sensitive information, app tampering, payment bypass, and privacy violations. Security is therefore required not only for servers and networks but also for the app itself, which runs on the user's device.

It is effective to combine multiple security technologies: not only source code obfuscation and encryption, but also anti-tampering, integrity verification, debugging and hooking detection, rooting/jailbreak detection, and RASP. LIAPP integrates these features to protect mobile apps in multiple layers.

LIAPP can detect and respond to a wide range of threats targeting mobile apps, including reverse engineering, app tampering, debugging, hooking, memory manipulation, rooting/jailbreaking, hacking tools, and abnormal runtime environments. The features available may vary depending on the OS and service configuration.

Official app store review alone cannot prevent every attack that occurs after an app is launched. Even a properly distributed app can be analyzed or modified on a user's device or targeted by runtime attacks, so additional security for the app itself is necessary.

Developers can implement individual security features themselves, but they then have to continuously develop and maintain features that respond to a wide range of attacks. LIAPP applies security to a completed app, which reduces the development team's burden of implementing and maintaining security.

Yes. LIAPP applies security based on the app file of a completed app, so it differs from approaches that require security code to be written directly into the app's source code.

A mobile antivirus is mainly intended to detect threats such as the device itself or malicious apps and files, whereas LIAPP protects the code and runtime environment of the protected mobile app itself. LIAPP therefore protects the app to which it is applied, not the entire smartphone.

Mobile app source code protection makes it difficult to analyze an app in order to understand its internal logic and sensitive information. LIAPP uses technologies such as obfuscation and encryption to reduce the risk of app analysis and code theft.

App analysis can expose sensitive information such as internal logic, API-related information, and security logic, which can lead to further attacks or infringement of intellectual property. It is therefore important to protect the code of the distributed app itself.

Obfuscation is a security technology that makes an app's code and structure difficult for an attacker to analyze and understand. It is used to raise the difficulty of reverse engineering and to protect the app's core logic and intellectual property.

Obfuscation is an important defense, but it cannot block every attack. It is effective to combine multiple security technologies such as anti-tampering, integrity verification, debugging and hooking detection, and RASP.

Reverse engineering is the act of analyzing a distributed app to understand its code, structure, and logic. LIAPP raises the difficulty of app analysis and protects critical code through obfuscation and encryption, anti-analysis measures, and debugging detection.

App tampering is an attack in which a legitimate app is analyzed and then its code or resources are modified to add malicious functionality or bypass existing functionality. LIAPP verifies the app's integrity and whether it has been modified, and detects and blocks abnormal app execution.

Yes. When the app runs, its integrity and whether it has been modified can be verified to confirm that it is a properly protected app. If tampering is detected, responses such as restricting app execution are possible according to policy.

RASP is a technology that detects and responds to security threats within the app's runtime environment while the app is running. LIAPP can detect a range of runtime threats such as rooting/jailbreaking, debugging, hooking, and tampering, and can respond according to policy.

Yes. LIAPP checks the app's runtime environment and can detect a variety of abnormal behaviors such as debugging, hooking, rooting/jailbreaking, and tampering. Detected threats can be handled according to the configured security policy, for example by restricting app execution.

Yes. Attackers can use debuggers, hooking tools, or memory manipulation tools to analyze or change an app's execution flow or data. LIAPP can detect and respond to such abnormal runtime environments and attack behaviors.

Hooking is an attack technique that intervenes in specific functions or processing flows while an app is running in order to analyze or change its behavior or data. LIAPP detects abnormal hooking-related behavior in the app's runtime environment to respond to runtime attacks.

LIAPP provides a variety of protection features to counter memory manipulation and game data tampering. By blocking memory access, detecting tampering, and encrypting the game's key variables, it protects the runtime environment and reduces the risk of abnormal manipulation of in-game currency, items, scores, and similar values.

LIAPP's hacking tool detection and similar features can respond to the abnormal environments used in payment bypass attacks. For secure payment processing, however, we recommend combining app security with a payment verification system such as server-side receipt validation.

On a rooted or jailbroken device, the operating system's basic security controls are weakened, making it more likely that the app and its data will be exposed to attacks. LIAPP can detect such environments and restrict app execution according to the security policy.

Depending on the configuration, you can choose whether to apply the rooting detection feature and still use the app. However, a rooted environment carries higher security risks than an ordinary device, so it is best to decide the policy based on the security requirements of your service.

Yes. Depending on your service's operational goals, the security policy can be configured to allow virtual machine or emulator environments. Settings that take the operating environment of mobile games into account are also possible.

Register the completed Android or iOS app file with LIAPP, configure the required security options, and apply protection. After testing the protected file that is created, you can distribute it to app stores following your existing release process.

Taking the app's structure and compatibility with external libraries into account, specific code or areas can be configured to be excluded from protection when necessary. The exact settings can be confirmed with the LIAPP technical support team based on your app environment.

Depending on how LIAPP is applied and the scope of support, additional work for the development team can be minimized. After protection is applied, we recommend running functional and compatibility tests in the actual service environment.

TEST is a feature for checking how LIAPP applies to your app and its compatibility before purchase, and a TEST build can only be used for three days. PROTECT is the feature used to apply LIAPP to an app for actual distribution using a formal license or ticket. Please check the policy of the product you are using for detailed conditions and usage periods.

The original app file used for applying LIAPP is uploaded in encrypted form and deleted after LIAPP has been applied, so it is safe.
The app file with LIAPP applied can be downloaded for three days, after which it is deleted.

First check for upload errors and verify the file format, file name, OS selection, and whether another security solution has already been applied. If the problem persists, contact the technical support team with your account information, app name, protection type, time of application, and the error message so that the cause can be identified.

For an app file with LIAPP applied, you can perform an initial check by confirming inside the file that LIAPP-related protection modules have been applied. Before actual distribution, however, you must always test installation and the behavior of key features.

Download the protected app file, complete the required signing and release preparation, and test installation, functionality, and compatibility on a real device. Once testing is complete, register the app with the store following your existing release process.

The basic app store release process is the same whether or not LIAPP is applied. However, because the app file (.apk, .aab, .ipa) is downloaded after LIAPP is applied, you may need to perform alignment and signing according to the file type before uploading it to the store.

First check the signing key, the Android signing method, the packaging state, debug settings, and store policies. If the problem persists, send the error message provided by the store along with your app information to the LIAPP technical support team.

All file sizes that can be uploaded to the distribution stores are supported. For large apps, uploads can be affected by network conditions, so we recommend proceeding in a stable network environment.

Depending on your environment, you can review the obfuscation results through the related information provided in the LIAPP console. The exact way to check may vary depending on the LIAPP product and protection settings you are using.

Installation problems can occur for various reasons such as signing, ABI mismatch, packaging, and Manifest settings. Check the error message and your app environment, and contact the technical support team if the issue is not resolved.

First check the protection options and compatibility with the app's internal libraries or the external environment. If the problem persists, send the protected app to the technical support team along with the device, OS version, and error message.

Yes. LIAPP supports Android and iOS mobile apps. However, because the two operating systems differ in structure and policy, the detailed security features that can be applied may differ.

Yes. LIAPP can be applied to the final Android or iOS build file of an app developed with Flutter. This makes it possible to apply code protection, anti-tampering, and runtime security features to Flutter-based apps as well.

Yes. Mobile apps developed with React Native can also have LIAPP security applied based on the final built Android or iOS app file.

Yes. LIAPP security can be applied to a variety of mobile app environments that use JavaScript, such as React Native, Cordova, and Ionic. The exact scope of protection may vary depending on the app's structure and build method.

Yes. LIAPP can be applied to Android and iOS mobile games developed with Unity. A variety of features needed for game security, such as code protection, anti-tampering, and runtime attack detection, can be applied.

Yes. LIAPP security can be applied to the final Android or iOS build file of mobile apps and games developed with Unreal Engine.

Yes. LIAPP can also be applied to Cocos-based mobile apps and games such as those built with Cocos2d-x and Cocos Creator.

Yes. LIAPP can be applied to iOS apps developed in Objective-C, and projects that use both Swift and Objective-C are also supported.

Yes. LIAPP can be applied to iOS apps developed in Swift as well as to mixed Swift and Objective-C projects.

Yes. Code protection, anti-tampering, and a variety of runtime security features can be applied to Java-based Android apps.

Yes. LIAPP can also be applied to Kotlin-based Android apps and to mixed Java and Kotlin projects.

Yes. If you modify the app itself or build a new version, you must apply LIAPP to the new app file again before distributing it. If you distribute a new app file without applying LIAPP, that version will not be protected by LIAPP.

Update contents are reflected in builds protected with that version of LIAPP and do not affect apps that have already been distributed. You can review the update contents through LIAPP's announcements and release notes and decide yourself whether to apply them; when you update your app, we recommend using the latest version of LIAPP for security and compatibility.

The protection of an app that already has LIAPP applied remains in effect, but mobile operating systems and attack techniques keep changing. To respond to new app versions and the latest security threats, we recommend continuously managing your LIAPP version and security settings.

The range of security policies that can be managed after distribution may differ depending on the LIAPP product and features you are using. If you need real-time policy management, please check which products and configurations support that feature.

LIAPP provides technical support for problems that arise while applying and operating it. For issues such as errors when applying LIAPP, compatibility, security settings, and execution problems, we identify the cause based on logs and the app environment and advise on how to respond.

LIAPP uses an asynchronous inspection method, so there is almost no difference in execution speed compared with the original app. Depending on the nature of the app, some security features perform additional security processing and may therefore affect performance in certain environments. We recommend testing your app's key features and performance before releasing it to production so that you can configure appropriate security settings.

Personal data must be protected not only through secure storage and transmission but also against attacks on the app itself. In addition to encrypted communication, secure authentication, and server security, it is important to combine multiple security layers such as anti-tampering, rooting/jailbreak detection, and runtime protection.

LIAPP only checks the device model and OS information in order to display statistics, and does not collect users' personal data.

Yes. Before formally adopting LIAPP, you can test it to confirm whether it can be applied to your app and to check its features and compatibility. Please check the current free trial policy for details such as the trial period and the features provided.

The products offered on the LIAPP site can be paid for after signing up and logging in. For payment methods that the site does not support or products that require a separate contract, you can receive guidance through a sales inquiry.

A Ticket is a consumable pass that lets you apply LIAPP once, while a Monthly License is a period-based license that lets you apply LIAPP to a registered app without a limit on the number of times during a set period. Please check the latest pricing policy for the products actually offered and the number of applications allowed.

For an app protected with LIAPP under a formal license, protection can remain in effect for that app version even after the license expires. However, a valid license may be required to apply protection to a new app version or to change security settings.

Yes. Annual contracts are available. For products that cannot be purchased directly on the website or for enterprise contracts, please check through a sales inquiry.

Purchased Tickets do not have an expiration date. However, because a Ticket is a single-use product that is consumed immediately when used, please be sure to check your app by applying TEST before using one.

After signing up, you can use the LIAPP console and the test and protection services provided. The features actually available may vary depending on your account and product status.

LIKEY is a mobile security keypad solution that protects the sensitive information users enter in mobile apps. It protects important input such as passwords, PINs, account numbers, and card numbers on a One Time Data basis, reducing the risk that entered information will be leaked.

Sensitive information such as passwords should be protected from the moment the user enters it. LIKEY converts information entered through the security keypad into one-time data, reducing the risk that the actual input will be exposed.

In mobile apps, users enter sensitive information such as passwords, PINs, account numbers, and card numbers during login, payment, transfers, and identity verification. Because the theft of such information can lead to the leakage of personal and financial data, it is important to protect the data safely from the input stage onward.

The main purpose of a normal keypad is to pass the information the user enters to the app, whereas a security keypad also takes into account the risk of information theft that can occur during input. LIKEY protects important input through security features such as a randomized keypad and one-time data generation.

LIKEY can protect important information entered through a mobile app's keypad, such as IDs, passwords, PINs, account numbers, and card numbers. It can be applied not only to financial information but also to a wide range of user input that a service needs to protect.

LIKEY generates One Time Data from the information a user enters through the virtual keypad and passes it to the server. This reduces the risk that the actual input will be exposed during the input and data transmission process.

One Time Data refers to single-use data that is newly generated each time in order to protect user input. Each time LIKEY receives initial data ("one-time random data") from the server, it generates different data even when the user enters the same value, which ensures strong security.

Yes. LIKEY generates different one-time data every time, even when the same value is entered. With a typical security keypad, data can easily be inferred through hacking techniques such as hooking and key loggers, but LIKEY receives "one-time random data" from the server when the keypad is activated, fundamentally preventing the leakage of user information.

If the keypad's buttons are always in the same position, attacks that analyze the user's touch positions or coordinate information to infer the entered values can occur. LIKEY randomizes the key arrangement and blank spaces to reduce the risk of this kind of input analysis.

LIKEY can randomly rearrange the key layout and blank spaces of the virtual keypad. This reduces the risk of attacks that infer the actual input from the positions or coordinates the user touched.

Yes. LIKEY lets you configure a variety of UI elements such as the keypad background, button size and color, font, button spacing, and borders. You can compose the security keypad to match your app's design or brand guidelines.

Yes. LIKEY supports NUMBER-style numeric keypads and QWERTY-style keypads. You can use the keypad that suits the type of input, such as login, PIN, account number, or card number.

Yes. Financial, fintech, and payment apps handle sensitive user input such as passwords, PINs, account numbers, and card numbers, so they are a representative field in which a security keypad is needed. LIKEY can also be applied to a wide range of other mobile services that collect personal or sensitive information.

Yes. LIKEY can be applied not only to native apps but also to mobile apps based on Flutter and React Native. The security keypad can be used in a variety of mobile app development environments.

LISS is a mobile screen security solution that prevents screen capture, screen recording, and screen sharing in mobile apps and detects remote control apps. It prevents important information displayed on app screens — such as personal data, financial data, authentication data, and content — from being leaked externally.

To prevent screen capture in a mobile app, you need to restrict the capture feature in the app or protect important information so that it is not saved when the screen is captured. LISS detects screen capture and renders protected screens as a blank screen (white or black), preventing important information from being captured.

Mobile app screens can display important information such as personal data, financial data, authentication codes, corporate information, and paid content. If such screens are captured and shared externally, problems such as personal data leakage or unauthorized copying of content can occur. Apps that handle important information therefore also need security for the screen itself.

Yes. LISS supports Android and iOS and can prevent screen capture in mobile apps. The detailed features supported may differ depending on the OS, device, and app environment.

Yes. LISS can block protected screens when the screen played or displayed in an app is recorded, preventing unauthorized recording. It can also be used to protect content delivered through the screen, such as videos, educational material, and paid content.

Yes. LISS can block protected app screens during screen sharing, preventing important information from being exposed on an external display. This helps prevent the leakage of personal data or important content that can occur during screen sharing.

Yes. LISS can selectively protect not only the entire app but also specific screens or UI areas that need protection, such as those showing personal data, financial data, or authentication data. This lets you keep the screen capture features needed for using the service while protecting only the important areas.

Yes. When a user switches to another app or views the recent apps screen, protected screens can be rendered in black. This prevents important screen information from being exposed even when the app is not actively in use.

If a remote control app is abused, an attacker can view the user's smartphone screen or operate it remotely to steal personal and financial data. LISS can detect whether a remote control app is running while the protected app is in use and respond to this kind of security risk.

LISS can detect that a remote control app is running while a protected app is in use. When a remote control app is detected, the screen can be blocked or the user can be notified, preventing important information from being exposed.

Yes. LISS can detect screen capture attempts or the execution of remote control apps and notify the user. This helps users recognize the security risk that is currently occurring and take the necessary action.

Yes. In financial and fintech apps, important information such as account details, transaction history, and authentication data is displayed on screen, so preventing information leakage through the screen is important. With LISS, you can apply capture, recording, and screen sharing prevention to these important screens.

LISS can be applied to apps that deliver important information or content through the screen, such as financial, fintech, healthcare, commerce, education, content, and enterprise apps. It is especially useful for services that need to prevent personal data, financial data, authentication data, or paid content from being leaked through the screen.

Yes. LISS supports not only Android and iOS but also a variety of development languages such as Objective-C, Swift, JavaScript, Java, and Kotlin, and it can be applied in Flutter environments as well.