Skip to content

Roadmap

Jonathan LEI edited this page Sep 24, 2016 · 2 revisions

Since this API is built on the Web WeChat, the ultimate goal of development is to achieve the same level of functionality of that of Web WeChat.

Meta

At the moment, WeChatAPI is able to retrieve user information, yet it is not user-friendly. For example, in the JSON from the response, "Alias" refers to the WeChatID while on the webpage it actually refers to the remark name you gave to that particular user.

  • Basic info
  • Better mapping

Session Handling

WeChatAPI currently handles session badly. It works but it fails to detect expiration of sessions sometimes. It also fails to restore login status occasionally. The reason is still under investigation.

  • Login
  • Basic session management
  • Save and restore login status
  • Advanced session management

Messaging

Messaging is the most important part of WeChatAPI. Currently only text messaging is supported.

  • Text messaging
  • Emoji mapping
  • Tuzki stickers mapping
  • Sending and receiving images
  • Sending and receiving files

Chats

In Web WeChat, users can start a group chat and add new members to the chat.

  • Group chat management

Others

WeChatAPI sends HTTP requests that are as simple as possible so as to save effort, meaning many headers or even web form data are missing. It work as of this writing. But it is theoretically possible for Tecent (the company that runs WeChat) to detect the usage of this very API. It's our goal to achieve 100% emulation.

  • Official account articles
  • Better emulation

Refining

  • Clearer and cleaner code comments / structures

Summary

The API aims to achieve the same level in terms of functionality with Web WeChat. There's still plenty of work to be done. Join us!

Project Management

Documentation

Clone this wiki locally