Long-deck and short-deck entry
The lobby shows separate game categories. Public shortTexas scenes, protocol files and controllers provide a starting point for reading the short-deck client.
See the product. Explore the code. Plan your poker project.
A visual starting point for Texas Hold’em client development, short-deck research and poker club evaluation. Review the actual screens and public modules before deciding what to build.
Discuss delivery scope →
The lobby shows separate game categories. Public shortTexas scenes, protocol files and controllers provide a starting point for reading the short-deck client.
Review room screens, club navigation and hand-record modules to map the player and management journey.
Original screenshots show insurance and history screens. Rules and calculations still require validation against the delivered implementation.
Images come from this repository’s Screencut folder and retain their original UI and marks. Page copy is translated; screenshots remain in Chinese and do not establish multilingual client support.

Review navigation between game categories and club features.

See the mobile layout for seats, cards and player actions.

Use the original room screen to discuss table-selection flows.

Inspect how insurance-related information appears during play.

Review the history interface and information layout.

The source image is named “可存证牌界面”. An image does not verify fairness or the validity of any proof mechanism.

The screenshot shows user, club and reporting menus. It does not establish that the corresponding admin source is public.
This repository presents source files and product material, not a verified one-click deployment. The public tree contains Cocos-style JavaScript client files and Lua backend modules. The C++ core, Vue 3 / Go admin and complete database/deployment materials described in the previous README require separate confirmation.
Code guide and delivery checklist →Explore lobby, table and admin screenshots and identify the flows you want to customize.
Check public modules, dependencies, engine versions and missing project files.
Request a runnable demo, build instructions, database scripts, license scope and acceptance criteria.
AKpoker appears in the repository name and KKPOKER appears in the original screenshots. Neither establishes official status, authorization, a partnership or adoption by either brand.
The lobby screenshot displays 永旺德州 (Yongwang Poker). The repository also includes long-deck and short-deck navigation, table, insurance and admin screenshots. These help evaluate product flows, but do not establish brand ownership, parity with a live app or a complete source-code delivery.
A complete build and deployment path has not been verified. Read the code guide and confirm the full project, runtime dependencies, database and deployment instructions with the maintainer.
The previous README mentioned these modes, but the public files do not establish a complete runnable implementation. Ask for a matching demo and delivery checklist if you need them.
The current LICENSE contains MIT license text. Refer to that file and the applicable rights for public code; confirm separate terms for unpublished projects, artwork, brand assets and custom work.
Share your target platforms, game modes and delivery needs with the maintainer to discuss a demo and source scope.