# TiebaLite HarmonyOS: A Third-Party Baidu Tieba Client Built on ArkUI and Asset Store Kit > TiebaLite HarmonyOS is an unofficial Baidu Tieba client for HarmonyOS NEXT, using native ArkUI components, Asset Store Kit for credential storage, and TaskPool for Protobuf decoding. It is feature-rich but carries clear limitations around login, device verification, and missing features. **137458/tieba-lite-harmony** — Tieba Lite, ported to HarmonyOS NEXT. - Repository: https://github.com/137458/tieba-lite-harmony - Stars: 54 · Forks: 2 - Language: PowerShell - License: not declared - Published: 2026-08-21 · Updated: 2026-08-21 · Language: en - Canonical page: https://hysenlabs.com/projects/137458-tieba-lite-harmony ## What TiebaLite HarmonyOS Actually Solves TiebaLite HarmonyOS addresses a gap: Baidu's official Tieba app is not built for HarmonyOS NEXT's native interface paradigms. This project reimplements the client using ArkUI and HarmonyOS Design System (HDS) components, so the UI matches system navigation, menus, floating bars, and materials. The target user is someone on a HarmonyOS NEXT phone or tablet who wants to browse and interact with Tieba without leaving the native ecosystem. The project is explicit that it is not affiliated with Baidu, so it is a third-party effort with all the risks that entails. It is not a port of the Android app; the README states the HarmonyOS side is an independent implementation, though it references Android and Python projects for API behavior and algorithms. ## How It Works: Native Components, TaskPool, and Asset Store Kit The architecture relies on HarmonyOS-specific mechanisms. The UI is built with HdsNavigation, HdsNavDestination, and HdsTabs, giving a native navigation structure. The post detail page uses an immersive layout with a native title bar and floating action bar. For performance, the project uses TaskPool to offload some Protobuf decoding, which is a concrete choice to keep complex post data from blocking the main thread. Login credentials are handled through the Asset Store Kit, which stores BDUSS and STOKEN in a secure asset store rather than plain configuration files. The README notes that the app attempts to extract credentials from login cookies, and STOKEN availability depends on what Baidu returns. This is a fragile point: manual BDUSS login is offered as a backup, but some operations still require STOKEN from web login. The design shows a deliberate effort to use system security features, but the dependency on Baidu's cookie behavior is a real constraint. ## Getting It Running: DevEco Studio and SDK Requirements The project targets HarmonyOS NEXT phones or tablets. To build it, you need DevEco Studio and a HarmonyOS SDK that matches the project's model version. The README states the current project model version is 6.1.1, but it does not pin an exact SDK version, saying the specific SDK depends on your local DevEco configuration. This means you must have DevEco Studio installed and likely need to adjust the SDK version to your environment. The repository does not provide a command-line build script in the README; the primary language is listed as PowerShell, but the README gives no PowerShell commands. So the practical path is to open the project in DevEco Studio, let it sync with the model version, and build from the IDE. There is no mention of signing or provisioning, but for a HarmonyOS app, you will need a developer certificate, which the README does not cover. That is a gap you must fill yourself. ## What Works and What Is Missing The feature list is substantial. Browsing follows, search, post details, 'view only the OP', reply sorting, and pagination are implemented. Interaction includes likes with rollback on failure, favorites, sharing, check-ins, and a reply box with text, emojis, and image upload. The reply sheet is a custom immersive sheet with a preview card for in-thread replies, which shows attention to detail. HarmonyOS-specific features include a customizable bottom tab bar (home is always present), four levels of immersive light effect intensity, dark mode, dynamic color extraction, and haptic feedback. Deep links are supported for tblite://thread, com.baidu.tieba://unidispatch, and https://tieba.baidu.com/p/ URLs, but other web paths are not guaranteed. However, the README lists significant gaps: no posting new threads, no draft box, no multi-account management, no complete browsing history or block management, and no desktop service cards or floating windows. Video playback is implemented but still needs real-device verification across different hardware. ## The Login and Security Trade-Off Login is a core risk. The app supports two methods: web login via an in-app browser and manual BDUSS entry. Web login tries to extract credentials from cookies, but STOKEN is not always returned. Manual BDUSS login is a backup, but operations requiring STOKEN still need web login first. Credentials are stored in Asset Store Kit, which is a security improvement over plaintext files, but the README warns that copying BDUSS to the system clipboard can expose it to other apps that read the clipboard. Also, the project does not guarantee that credentials survive uninstall or backup restore, depending on system and Asset Store Kit policies. This is a clear limitation: if you rely on persistent login, you may need to re-authenticate after a reinstall. The README also mentions a one-time migration for old credentials, which cleans up old keys, but that is a one-time process. For privacy-conscious users, the clipboard exposure is a concrete concern that the project itself acknowledges. ## Maintenance and Upgrade Cost The project is active, with recent releases including v1.2.3-rc.1 in August 2026 and v1.2.2 before that. The release cadence suggests ongoing development. However, the README indicates that some features are code-complete but not fully verified on real devices, so you should expect updates that fix device-specific issues. The project references several external projects for API behavior, including aiotieba and tbclient.protobuf. These are not runtime dependencies, but they mean the project relies on reverse-engineered interfaces that could break if Baidu changes its API. Upgrading may require tracking changes in those reference projects. The license is listed as unknown in the repository metadata, and the README warns that using or distributing code from referenced projects must comply with their respective licenses. This is a legal ambiguity you should resolve before adopting the code for anything beyond personal use. The project itself does not state a license, so you have no clear terms for redistribution. ## Alternatives and Why This One Is Different The main alternative is the official Baidu Tieba app, but it is not built for HarmonyOS NEXT's native design language. Another alternative is using the mobile web version of Tieba in a browser, which works on any device but lacks system integration like haptic feedback, native navigation, and Asset Store Kit security. TiebaLite HarmonyOS differs by wrapping the web login in an in-app browser and using system APIs for credential storage and task offloading. A more technical alternative is to use the aiotieba Python library directly, which gives you scripted access to Tieba APIs without a UI, but you would have to build your own client and handle Protobuf decoding yourself. The difference is that TiebaLite provides a ready-made UI and native experience, while aiotieba is a library for automation. If you need a GUI client, this project is one of the few options; if you need programmatic access, aiotieba is more appropriate. The trade-off is that TiebaLite is tied to HarmonyOS, so it is not portable to other platforms. ## Conclusion: Who Should Adopt It and What to Verify Adopt TiebaLite HarmonyOS if you are a HarmonyOS NEXT user who values native UI integration and is willing to accept the limitations of a third-party client. Do not adopt it if you need to post threads, manage multiple accounts, or require guaranteed login persistence. Before using it, verify that your device is supported for features like video playback, test the web login to see if STOKEN is obtained, and check whether the Asset Store Kit credentials survive an uninstall. Also, confirm the project's license status, as the repository does not specify one, which could affect your ability to modify or redistribute the code. The project is a serious effort to bring Tieba to HarmonyOS, but its reliance on reverse-engineered APIs and unverified device behavior means you should test it on your specific hardware before relying on it daily. ## Conclusion Adopt TiebaLite HarmonyOS if you are a HarmonyOS NEXT user who wants a native-feeling Tieba client with deep system integration and are comfortable with its unofficial status and login caveats. Do not use it if you need multi-account support, posting capabilities, or guaranteed credential persistence across reinstalls. Before adopting, verify that your device is supported, test the login flow thoroughly, and confirm that the Asset Store Kit behavior meets your expectations for credential security. ## FAQ ### Who owns Tieba, the service tieba-lite-harmony talks to? Baidu. This project states that it is a third-party Baidu Tieba client with no subordination or authorisation relationship with Baidu, and its disclaimer tells users to follow Baidu Tieba's own terms of service and the law of their region. ### What is Tieba, from the point of view of tieba-lite-harmony? It is Baidu's forum platform, and the client works against its structure: followed forums on the home page, forum post lists and featured content, post detail with floor-level replies, whole-site and in-forum search, and hot topics with their own detail pages. The client is built for HarmonyOS NEXT phones and tablets. ### How does tieba-lite-harmony store Baidu credentials? BDUSS and STOKEN are kept with the HarmonyOS Asset Store Kit rather than in a plaintext config file, after a one-time migration that clears older credential keys. Whether a STOKEN arrives from the web login depends on the cookie Baidu returns, and a BDUSS the user copies to the system clipboard can be exposed to clipboard readers. ### What has tieba-lite-harmony not finished yet? Creating top-level threads and drafts, multi-account management, complete browsing history and blocking, and home screen service cards or floating windows. The project also states that some HarmonyOS features are code-complete but still need real-device verification across different devices and system versions. ## Sources - [Official README](https://github.com/137458/tieba-lite-harmony#readme) - [Project repository](https://github.com/137458/tieba-lite-harmony) - [Release notes](https://github.com/137458/tieba-lite-harmony/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/137458-tieba-lite-harmony