Krita

Open Krita on an Android tablet and you are looking at the same interface that runs on a desktop workstation. The toolbar is dense. The brush engine is ready. The layer stack is visible. No simplified mobile version. No dumbed-down controls. This is the full Krita experience, ported directly to Android. The app does not hold your hand. It expects you to know what you are doing or to be willing to learn. The canvas is blank. The brushes are numerous. The learning curve is steep. That is the trade-off. You get professional-grade tools for free, but you have to figure out how to use them.

The Android version is still in beta. The Play Store listing explicitly states that it is not suitable for real work yet. That warning is important. The app crashes. The interface is not optimized for phones. It is designed for tablets and Chromebooks. The screen real estate requirement is significant. You cannot zoom out enough on a small screen to see the full interface. The app works best on devices like the Samsung Galaxy Tab S9+ or the Galaxy Fold. The developer does not hide this limitation. It is stated clearly in the description. The app is a work in progress on mobile, but it is already functional enough for many artists.

The Brush Engine and Layer System

The brush engine is the heart of Krita. It offers over 100 brush presets, including pencils, inks, watercolors, and oils. Each brush is highly customizable. You can adjust size, opacity, flow, spacing, and texture. The brushes respond to pressure and tilt. The stabilizer helps with smooth inking. The assistants help with perspective and complex scenes. The brush engine is widely considered superior to Photoshop's for painting. The sliders work well on Android, especially in version 5.3. The selection actions popup is a welcome addition.

The layer system is equally powerful. You can create multiple layers, adjust blend modes, and apply layer styles. The non-destructive editing features are a standout. Filter masks and transform masks let you apply effects without permanently altering the original layer. That is a professional workflow. The layer system supports PSD files, so you can move work between Krita and Photoshop. The layer stack is familiar to anyone who has used desktop painting software. The only issue is that reordering layers and moving them into groups is difficult without a keyboard on Android. That is a usability gap that needs addressing.

The interaction between the brush engine and the layer system is where Krita shines. You can paint on a layer, apply a filter mask, and adjust the effect in real time. The brush strokes update instantly. The mask shows the result immediately. That feedback loop is fast and responsive. It works the same on Android as it does on desktop. That consistency is rare. Most mobile painting apps simplify the layer system or limit the brush engine. Krita does neither. It gives you the full desktop experience on a tablet. That is the app's defining strength.

This is where the original analysis comes in. The interaction between the layer system and the brush engine creates a specific workflow advantage. The non-destructive editing features—filter masks and transform masks—allow you to experiment without committing to changes. You can paint a stroke, apply a blur filter mask, and adjust the blur amount later. The brush engine continues to work normally. The mask does not interfere with the painting process. That is different from Photoshop, where filter effects are often applied destructively unless you use smart objects. Krita's approach is more flexible. The workflow is more fluid. You can iterate faster. The only limitation is that the Android version does not always handle complex masks well. The app can crash when too many layers and masks are active. That is a stability issue, not a design flaw.

Animation and Python Scripting

Krita supports frame-by-frame raster animation. The feature was added through a Kickstarter campaign in 2015. The animation tools include a timeline, onion skinning, and audio playback. The workflow is timeline-based. You create keyframes on layers. The app interpolates between frames. The animation tools are not as advanced as dedicated animation software, but they are functional for short loops and animatics. The Android version supports animation, but the performance depends on the device. The app keeps all frames in memory, which can be a problem on devices with limited RAM.

Python scripting is another advanced feature. Krita provides a Python API that allows users to write scripts and plugins. You can automate repetitive tasks, create custom dockers, and extend the app's functionality. The scripting support is powerful. It is one of the reasons Krita is popular among technical artists. The Android version supports Python scripting, but the implementation is less tested. Some users have reported issues with Python scripting on mobile. The feature works, but it requires some technical knowledge to use effectively.

The combination of animation and Python scripting is unique. You can write scripts to automate animation tasks. You can create plugins that add new animation features. The potential is significant. The Android version brings that potential to a mobile device. You can animate on the go. You can run scripts on a tablet. The experience is not as polished as the desktop version, but it is functional. The app is a work in progress on mobile, but the foundation is solid.

Performance, Bugs, and the Free Experience

The Android version has stability issues. The app crashes on startup for some users. The crashes are often related to missing libraries or resource copying. The developer has released several fixes. Version 5.3.1.1 addressed a crash on Android 12 and older when accessing text controls. Version 5.2.13 fixed crashes caused by background saving. The fixes have improved stability, but the app is still not crash-free. Users report that the app is more stable in version 5.3. The improvements are noticeable, but the app is still beta software.

The interface is another pain point. The app is not optimized for phones. The UI elements are large. The toolbars take up screen space. You cannot zoom out enough to see the full interface on a small screen. The app works well on tablets and Chromebooks, but it is unusable on phones. The developer has acknowledged this limitation. The app is designed for big screen devices. The phone experience is not a priority. That is a significant barrier for users who want to use the app on a phone.

The text tool is a specific point of frustration. Version 5.3 introduced a new WYSIWYG text tool. The tool is more powerful than the previous version, but it is harder to use. Users have complained about the complexity. The tool requires more steps to achieve simple results. The text tool on Android is even more limited. Editing text fields on Android 12 or older caused crashes until version 5.3.1.1. The text tool is a work in progress. It needs refinement.

The storage permission issue is a recurring problem. Some users report that the app cannot access storage after system updates. The app does not have a storage permission toggle in the settings. That prevents the app from saving files. The issue is device-specific, but it is a significant blocker for affected users. The developer has not provided a clear solution. The workaround is to reinstall the app or grant permissions through the system settings, but that does not always work.

The app is completely free. There is no subscription. There are no locked features. The in-app purchases are donations. You can buy supporter badges or subscribe to support development. The purchases do not unlock any functionality. They are purely optional. That is a remarkable business model. The app is free forever. The open-source license guarantees that. The app is available on multiple platforms. The Android version is free. The desktop version is free. The source code is available. That is the core value proposition. You get professional-grade software at no cost. The trade-off is that the Android version is still in beta. The stability issues are the price of free software.

The app's cross-platform capability is a major strength. The same app runs on Windows, macOS, Linux, and Android. The interface is nearly identical across platforms. That consistency is rare. Most painting apps have different versions for mobile and desktop. Krita does not. You can start a project on a desktop, continue it on a tablet, and finish it on a laptop. The file format is the same. The features are the same. The workflow is the same. That is a significant advantage for artists who work across multiple devices.

The app's community is active and supportive. The Krita Artists forum is a hub for users and developers. The subreddit has 159k members. The community provides tutorials, resources, and feedback. The developer listens to user feedback. The app improves with each release. The community is a valuable resource for new users. The learning curve is steep, but the community helps flatten it.

The app's system requirements are reasonable. The minimum RAM is 4GB, but 16GB is recommended for heavy use. The app requires OpenGL 3.0 or higher. The Android version requires Android 4.4+. The performance depends on the device. High-end devices handle the app well. Low-end devices struggle. The app is resource-intensive. The brush engine and layer system require significant processing power. The animation tools are even more demanding. The app is not suitable for budget devices.

The app's future is promising. The developer is actively working on the Android version. The 5.3 release brought significant improvements. The 5.3.3 release added in-app donations. The 6.0 beta is in development. The Android version will continue to improve. The mobile makeover is planned. The app will eventually be optimized for phones. The timeline is uncertain, but the direction is clear. The app is a long-term project. The foundation is solid. The potential is enormous.

One specific technical detail that stands out is the Android platform plugin packaging issue. Version 5.3.x was crashing on startup because the Android platform plugin was missing from the APK. The issue was caused by a change in the build process. The fix was to skip the plugins/platforms/ folder on Android. That is a niche technical detail. It affects a small number of users. But it highlights the complexity of porting a desktop application to mobile. The developer is working through these issues. The app is improving. The bugs are being fixed. The future is bright, but the present is still a work in progress.