mrkeyoor.comAsk

TG-Twilight/c001apk

c001apk review

Use TG-Twilight/c001apk if you read Coolapk in Chinese and want selective post exports or a Flutter client to customize.

Not run yet

Webevaluationupdated 15 Nov 2026
+53stars / 7d

TG-Twilight/c001apk is an unofficial Coolapk client based on c001apk-flutter. Its Simplified Chinese README focuses on Android and Windows and documents reading, image viewing, local controls, and individual-post export.

Verdict

Use TG-Twilight/c001apk if you read Coolapk in Chinese and want selective post exports or a Flutter client to customize. Skip it if complete cloud-favorites backup, automatic migration, or uninterrupted account access is a requirement. The useful evidence is the documented export workflow and attributed user reports; our recorded setup stopped at prerequisites.

c001apk infographic: read Coolapk and save selected posts, plus its uses, what we have not run yet, pitfalls and who it suits
We have not run c001apk yet; the middle band lists what our review has not tested.

We ran it

Screenshot of c001apk (github.com/TG-Twilight/c001apk)
github.com/TG-Twilight/c001apk

Answers from our run

Did you run c001apk yourself?

No. Its code is Dart, and it carries no manifest our lab installs from, and no Dockerfile, so there was nothing standard to install, build or test. This review is written from the repository's own documentation.

Who should not use c001apk?

Readers whose main requirement is bulk cloud-favorites search and backup.

What are the alternatives to c001apk?

coolapk-desktop, 酷安开源版. Use TG-Twilight/c001apk if you read Coolapk in Chinese and want selective post exports or a Flutter client to customize.

SetupN/AThe runner stopped at prerequisites; installation was not reproduced in a supported application environment.
Docs4/5The README has an install section (“下载安装”) and a usage section (“使用说明”); we did not run its quickstart ourselves, and the README is mostly in Chinese, not English.Editor’s note: The supplied Chinese README documents exports and packages, but setup and the linked development guide were not evaluated.
Community4/5Last push on 2026-11-08, 942 stars and maintainers answered or closed 10 of the 10 most-discussed issues we sampled.Editor’s note: Sampled issues contain maintainer replies and user patches, without measuring support availability or adoption.
Maturity2/5Latest release 1.5.2-release on 2026-11-08 and repository created 2026-10-14.Editor’s note: Repository activity and release records are supplied, but application reliability and migration were not exercised.

How we score

Who it’s for

Coolapk readers comfortable with a Chinese README who want to save selected posts as Markdown or offline HTML.
Android users who can match a problem to a specific version and issue report.
Developers interested in customizing the Flutter client, as contributors describe in issues #16 and #18.

Who it’s NOT for

Readers whose main requirement is bulk cloud-favorites search and backup.
People who need complete discussion exports, including nested replies and video.
Users who require automatic migration of accounts and local favorites from another client.
People whose choice depends on uninterrupted account access.

Setup reality

Our configured sandbox had 3 CPUs and 8 GB RAM, with image n/a, at commit e9ad0ce on 2026-11-15. The harness recorded NOT RUN because it supported no Dart ecosystem and found no Dockerfile. The separate Compose prerequisite check found zero of its four accepted filenames and stopped before application execution.

The README directs users to release packages. For Android it lists three architectures and Android 7.0 as the minimum. For Windows it instructs users to extract the complete directory and retain the DLLs and data folder beside c001apk.exe. The README corresponds to 1.5.2; the inspected checkout is e9ad0ce, while the release page identifies 1.5.2-release with c034b98.

TG-Twilight/c001apk suits Coolapk readers who want to save selected posts or customize a Flutter reading interface. It is a poor choice when the deciding requirement is a complete cloud-favorites backup. The README documents individual-post export, while issue #17 asks for bulk retrieval, local search, and export of existing cloud favorites. That difference matters more than the number of features in the project description.

The repository identity also matters. This review covers TG-Twilight/c001apk, whose README names c001apk-flutter as its base and focuses on Android and Windows. A tutorial or archive notice for another c001apk repository answers a different question. Start with the owner and repository name when comparing installation advice, architecture descriptions, or reports of maintenance, then match the version and symptom to the relevant source.

What people use c001apk for

Users report reading posts, saving content, and modifying navigation in personal builds. The five examples below describe different tasks: ordinary browsing, selective preservation, interface customization, a window workaround, and account interaction. Keeping the task beside the reported outcome helps distinguish a reason to choose the client from a change someone made to their own copy. Each example links to its issue record.

Who used it What they did Reported outcome
The requester in issue #18 Scrolled through posts and switched sections with horizontal gestures Wanted persistent navigation bars hidden to leave more reading space. Navigation request
IamNewHands Changed navigation in a personal fork Reported hiding both bars after scrolling and revealing them with a sustained upward gesture lasting one second. Personal navigation change
CDXIII Used content saving Said it addressed original-c001apk compatibility problems, while requesting bulk cloud-favorites access. Content-saving report
X5426X Patched and rebuilt 1.3.5-release, commit fb3e06c, for a HyperOS floating window Reported normal floating-window rendering, full-screen rendering, and switching between them. Local patch report
The reporter in issue #12 Configured protocol and device information Could comment, but following a topic displayed an error. Topic-follow report

The project README documents feeds, articles, comments, search, guest mode, local favorites, and browsing history. For preservation, it describes exporting the body, author, source, and some comments as Markdown or offline HTML, with images optionally embedded in the HTML file. That gives selective saving a concrete workflow: open a particular post, save its content, and inspect the resulting file outside the client.

What happened when we ran it

Our run stopped before application execution at commit e9ad0ce on 2026-11-15. The configured sandbox had 3 CPUs and 8 GB RAM, with image n/a. The harness recorded no supported Dart ecosystem and no Dockerfile. Separately, the Compose safety check found zero of four accepted filenames, so that route stopped at its prerequisite check. These observations describe the runner and its decision, rather than an Android launch result.

Recorded item Result Meaning for this review
Source checkpoint e9ad0ce, 2026-11-15 Identifies the checkout in the lab record.
Sandbox configuration 3 CPUs, 8 GB RAM, image n/a Records the configured sandbox.
Ecosystem route NOT RUN: no supported ecosystem, language Dart; no Dockerfile Installation, build, and tests were not executed.
Hands-on safety step FAILED: zero of compose.yaml, compose.yml, docker-compose.yaml, and docker-compose.yml were present The Compose route stopped before application execution.
Teardown ok The record reports cleanup.

The safety record calls the repository "unsafe" because that harness rule requires a Compose file. Its concrete finding is the missing prerequisite. A separate run entry says Docker Compose deployed the project with every port bound to 127.0.0.1. The failed prerequisite and the harness's explicit NOT RUN result contradict that entry, so the deployment sentence cannot serve as evidence of execution. Teardown being recorded as ok does not resolve the contradiction.

Where people get stuck: match the symptom first

Issue #12 describes a topic-follow action that succeeded on the server while the client displayed an error. That is a different failure from repeated verification or a blank feed. The tracker is most useful when read as a symptom map: identify the affected action, read the maintainer's response, and keep a personal workaround separate from a released change. The table preserves those distinctions without treating every access error as the same problem.

Symptom and source What the record says Response in the thread
Repeated verification when opening comments, issues #1 and #3 Users describe repeated prompts after verification The maintainer said the latest version solved #1 and recommended the latest version in #3. Issue #1, issue #3
Empty feed and server-response-format error, issue #26 A participant suggested importing another device's identifier; the reporter said other clients browsed normally The account-block explanation was disputed by the reporter. Issue #26 discussion
Topic following reports missing data, issue #12 The maintainer said the successful server acknowledgment omitted the data field The maintainer reported correcting response handling, adding follow/unfollow regression checks, and later closed the issue with "fix". Issue #12 response
HyperOS floating window shows only the bottom bar, issue #16 X5426X described displaced content and rebuilt 1.3.5-release locally The maintainer recommended updating HyperOS and declined a global workaround; X5426X reported success with a local Android padding patch. Issue #16 discussion
Content-filter controls overlap the status bar, issue #20 The report concerns unclickable controls on OnePlus 15 with ColorOS 17 The maintainer acknowledged the problem and reported completing a fix pending release. Issue #20 response

Issue #23 illustrates what a useful report needs. Its requester said the app displayed a server-response-format error on opening while login worked; the maintainer objected to missing reproduction information and screenshots. The README requests platform, version, reproduction steps, and redacted errors. Follow that format when reporting a similar symptom. In issue #12, the fact that commenting worked was particularly useful because it separated the topic-follow response problem from general account setup. Reporting discussion

Image changes in 1.5.2 address a specific gesture

The 1.5.2 release notes describe a fix for slow horizontal swipes in Android's large-image viewer, including swipes across live-image black borders. They also describe the new "我不想看HDR" setting. The maintainer points to the same changes in issue #25. If your complaint concerns moving between large images, this is the relevant release entry to read before changing unrelated settings. 1.5.2 release notes

Issue #25 also contains reports of dropped frames on the home screen and secondary pages. One user names a device running at 120 Hz; another names a Samsung S24 with adaptive refresh rate. The maintainer suggested checking refresh-rate restrictions. Those comments describe navigation and scrolling, whereas the release entry describes an image-viewer gesture. Keep the affected screen in your report so the image change and navigation complaint remain distinguishable. Image and scrolling discussion

Automatic navigation hiding has its own thread. IamNewHands describes hiding the top and bottom bars after scrolling and revealing them with a sustained upward gesture. The maintainer discusses a possible future interaction and calls it a longer-term plan. This is useful evidence for developers considering a fork: a user changed the reading interface to suit their habits. It is also a reason to check whether an example concerns the mainline package or a personal build. Navigation customization

Saving a post differs from backing up cloud favorites

Issue #17 remains an open request for bulk cloud-favorite search and export. CDXIII wants saved post text cached locally, optional images, local searching, and a way to identify posts that disappear. The maintainer points to existing content saving and says they will consider the request. CDXIII acknowledges that saving helped with original-client compatibility while continuing to request access to older cloud favorites and bulk preservation. Cloud-favorites request

The README says an export contains at most three top-level comments and excludes the full comment collection, nested replies, and video. Failed image downloads prompt for confirmation. These are file-content rules worth checking against your preservation goal: keeping an article's text is different from preserving the discussion beneath it. The same README says accounts and local data do not migrate automatically between clients with different package names. Export and migration instructions

CDXIII separately warns that other branches may not read the original client's local-favorites format and that uninstalling the original loses those favorites. Keep the original installed while examining readable copies of material you need. A practical first task is to export one representative post, open the file elsewhere, and inspect its images and comments. That recommendation follows the documented export contents and the user's migration concern; it does not require assuming that a new installation transfers an old collection.

Chinese documentation and local controls shape the workflow

The supplied README is in Chinese and describes a Simplified Chinese client. Its local-following feature stores a list on the device without sending an account-follow action, and the list does not automatically sync to the account. Content filtering is disabled by default and affects local presentation. The README also says filtering does not call account blocking or reporting interfaces. Those distinctions explain what changes locally when you adjust the reading experience. Local-control documentation

For installation, the README corresponding to 1.5.2 lists Android arm64-v8a, armeabi-v7a, and x86_64 packages, with Android 7.0 as the minimum. Windows users receive an x86_64 archive and must keep its DLLs and data folder beside c001apk.exe. For repeated verification, the README describes actively obtaining a device identifier during onboarding or in device settings, or importing one manually. It says acquisition does not happen automatically on launch or return to the foreground.

c001apk vs coolapk-desktop and 酷安开源版

The issue #17 requester names coolapk-desktop 1.34.1 and 酷安开源版 1.35.0 as alternatives. Their task is preserving and searching cloud favorites, which gives the comparison a concrete purpose. The coolapk-desktop README adds direct documentation of integrated cloud favorites and favorites collections. Compare that interface with the individual-post export documented by TG-Twilight/c001apk, then inspect the output you need to keep. Requester's alternatives

Candidate Evidence behind the comparison When to consider it
TG-Twilight/c001apk Its README documents Markdown and offline HTML exports; CDXIII reports useful content saving You want to preserve selected posts.
coolapk-desktop Its README documents cloud favorites and favorites collections; CDXIII names 1.34.1 and cites it as an indexing reference You want to investigate a cloud-favorites management interface.
酷安开源版 CDXIII lists version 1.35.0 among current alternatives You can resolve the exact project identity before evaluating its workflow.

The coolapk-desktop README identifies an unofficial desktop client based on Tauri 2, Vue 3, and Rust. TG-Twilight/c001apk names c001apk-flutter as its base. This is a supported architecture distinction and a useful starting point for someone choosing code to customize. The alternatives table deliberately ties each candidate to the preservation task instead of assigning an overall winner from unrelated feature descriptions. coolapk-desktop README

What the other reviews get wrong

The 2024 CSDN tutorial points to bggRGjQaUbCoE/c001apk, whereas this review covers TG-Twilight/c001apk. Its Jetpack Compose and MVI description therefore belongs to its stated repository context. The correction is to prevent that description from being transferred to this target, rather than to claim the tutorial identifies itself as a TG-Twilight review. The target README names c001apk-flutter, and issue #16 describes a local Flutter application patch. Tutorial repository reference

Repository or listing What the inspected source identifies
bggRGjQaUbCoE/c001apk The original repository, archived on May 11, 2024. Archive notice
TG-Twilight/c001apk The target, based on c001apk-flutter and focused on Android and Windows. Target README
LucaModric/c001apk A separate c001apk-flutter variant describing personal changes. Variant README
KiritoXDone/c001apk A separate Kotlin and Jetpack Compose client using miuix and developed from c001apk-compose. Compose client README

The target's repository metadata records a last push on November 8, 2026, and its release page identifies 1.5.2-release. Those facts distinguish it from the archived original. The supplied X post recommends c001apk to people interested in tinkering with Android clients, while the SourceForge mirror points to the original repository. Read each listing's destination before using its description to choose a package or interpret maintenance status. Repository metadata, X post, mirror identity

FAQ

Users report browsing and commenting with TG-Twilight/c001apk. The issue #12 reporter could comment after configuring protocol and device information, and issue #18 describes scrolling through posts and changing sections. Those reports answer the basic question of whether people use a third-party client for Coolapk. The remaining questions concern particular actions, versions, and preservation needs, so each answer points to the relevant documentation or discussion.

Can I still use a third-party client such as c001apk for Coolapk?

Yes, users describe browsing, commenting, and saving content. Issue #12 includes a report of working comments, issue #18 describes ordinary reading, and CDXIII discusses using content saving in issue #17. Those are concrete reported uses of the target. For the choosing decision, focus on which of those tasks you need, then read the corresponding section above rather than treating all account actions as one feature. Commenting report

Why does c001apk repeatedly ask for human verification when I open comments?

Issues #1 and #3 describe repeated verification, and the maintainer directs users to the latest version. The README adds an actionable route: actively obtain a device identifier in onboarding or device settings, or follow its manual-import instructions. Use the verification thread and the current README together when identifying the next step for that symptom. Verification reports, identifier instructions

How do I fix the server-response-format error and an empty feed?

Issue #26 contains a device-identifier suggestion and a disagreement about its explanation. A participant reports recovering with another device's identifier; the original reporter says other clients browse normally. Issue #23 adds the reporting lesson: supply the client version, platform, reproduction steps, and redacted error. Those details give a maintainer something concrete to investigate. Response-error discussion, reporting discussion

Why does a HyperOS floating window show only c001apk's bottom bar?

X5426X attributes the displaced interface to Flutter window-padding values in HyperOS floating-window mode and reports a local patch based on 1.3.5-release, commit fb3e06c. The maintainer recommends updating HyperOS and declines a global workaround. The detailed symptom map above keeps those two responses together so a system-update suggestion and a modified application remain clearly attributed. Floating-window thread

Can c001apk's page animations and scrolling be made smoother?

The maintainer advises checking refresh-rate restrictions in issue #25. The same discussion includes user reports at 120 Hz and on a Samsung S24, alongside a separate reply about 1.5.2 image-viewer changes. Identify whether your symptom occurs in the home feed, a page transition, or the image viewer before choosing the relevant advice. The image section above explains that distinction. Scrolling discussion

Can I disable HDR and improve swiping through large or live images?

Version 1.5.2 adds the "我不想看HDR" setting and describes image-swiping fixes. The README says the setting changes static large-image display while preserving live playback and original-file saving. Look under browsing and privacy for the setting, and use the release notes to match the slow-horizontal-swipe symptom to the documented change. HDR instructions, 1.5.2 changes

Can the top and bottom navigation bars hide automatically while I scroll?

IamNewHands reports implementing automatic hiding in a personal fork, including a one-second upward gesture to reveal the bars. The maintainer discusses a longer-term interaction idea in response. For a developer, the thread gives a concrete example of customization; for someone downloading the mainline package, its attribution to a personal fork is the useful distinction. Navigation thread

Why does following a topic report an error even though commenting works?

The maintainer says the server successfully followed the topic but returned an acknowledgment without the data field the client expected. The client interpreted that response as missing data and displayed failure. The maintainer reports correcting response compatibility and adding follow/unfollow regression checks, then closes the thread with "fix". This explains why working comments and a topic-follow error could coexist. Topic-follow explanation

How can I fix content-filter buttons overlapping the status bar?

The maintainer acknowledges the overlap in issue #20 and reports completing a fix pending release. The report concerns OnePlus 15 with ColorOS 17 and controls positioned in the status-bar area. Match those device and interface details to your symptom, then consult release information for the completed change. The troubleshooting table above preserves the maintainer's stated release status. Filter-control discussion

Can I search, bulk-save, and export my cloud favorites?

Issue #17 requests that combined workflow and remains open. CDXIII distinguishes existing content saving from retrieving older cloud favorites, caching their contents, searching locally, and preserving them in bulk. For selected posts, the README documents Markdown and offline HTML saving. For the collection-wide task, the request and comparison section explain why the two workflows should be evaluated separately. Bulk-favorites request

Will my original c001apk local favorites survive switching forks or uninstalling the original app?

The README says accounts and local data do not migrate automatically between differently packaged clients. CDXIII also warns that other branches may not read original local favorites and that uninstalling the original loses them. Keep the original available while checking readable copies of the material you need. The export section above describes what those saved files include. Migration warning, package-data instructions

What we have not tested yet

Application installation, builds, tests, and account workflows were not executed in our sandbox. The stopped run supplies no APK or Windows launch result, resource-use measurement, installation assessment, or test-coverage result. The configured image label also does not identify an operating-system or runtime version. The generic deployment entry conflicts with the failed prerequisite; its wording is not a security assessment or proof of a running application.

The inspected checkout e9ad0ce is distinct from the release page's c034b98 checkpoint for 1.5.2-release. Reported fixes remain attributed to maintainers or users: our lab did not exercise the image changes, topic-follow handling, HyperOS patch, or filter controls. The issue #20 extract names no containing release. General navigation-stutter resolution, device-wide image improvements, long-term reliability, and a complete original-favorites migration procedure are untested here. Issue #26 supplies no confirmed general repair for its response error.

The supplied documentation establishes a Chinese README, not the contents or language coverage of the linked development guide or every interface string. Linux runtime acceptance is pending in the README; its iOS artifact is an unsigned arm64 IPA requiring signing, also pending runtime acceptance. Device-identifier acquisition or import does not promise permanent freedom from verification, and the README retains login, verification, and server-interface restrictions. Alternative-client speed, complete backup behavior, and the exact repository behind 酷安开源版 remain outside this comparison.

Account safety also needs separate evidence. The historical Hovthen page warns about possible bans, but the records provide no measured incidence or causal finding. Identifier handling, network traffic, and local account storage received no security review here. Independent experience is limited: SourceForge invites the first review, the supplied Bilibili results concern unrelated subjects, and no independent hands-on lab, Reddit, or YouTube record is supplied. Promotional posts and repository attention do not answer those questions. Historical warning, SourceForge review listing, Bilibili results

Alternatives

ProjectWhat it isPick it when
coolapk-desktopAn unofficial client whose README identifies Tauri 2, Vue 3, and Rust and documents integrated cloud favorites.Consider its documented cloud-favorites interface if managing saved material drives your choice. The issue #17 requester names version 1.34.1 and points to this project as an indexing reference.
酷安开源版The other client named by the cloud-favorites requester, at version 1.35.0.Use the name and version as a lead when investigating the requester's alternatives. Resolve the exact project identity before choosing a repository or installation package.

Sources

  1. TG-Twilight/c001apk README
  2. GitHub repository facts
  3. c001apk 1.5.2 release notes
  4. Cloud favorites request and migration concerns
  5. Navigation and image-viewer discussion
  6. coolapk-desktop README

More web reviews