AI Weekly Malaysia

At OpenAI's Dev Day on September 29, 2026, the company announced agentic assistants called Dots, new AI models, and a set of changes that together turn ChatGPT into a distribution surface for third-party software. ChatGPT (stated at 1.2 billion weekly users) will start suggesting apps inside the conversation when it detects one could complete the user's task, the plugin architecture now supports extensions so developers can build interactive panels that run inside the chat, and users can carry their ChatGPT identity and existing AI allowance into third-party apps. The article frames this as a direct challenge to the traditional app store discovery model, but the excerpt is truncated and contains no pricing, launch dates, or country availability.

Why: If you ship a SaaS or an app, ChatGPT is being pitched as a new discovery and runtime channel alongside the web and mobile app stores — meaning your integration work and onboarding flow may need to work inside a chat panel, not just a browser. The portability of ChatGPT identity and AI allowance into third-party apps is the detail to watch: it changes whether users pay you directly or spend an allowance they already have, which affects pricing and conversion. Note that the text says nothing about rollout dates or whether Malaysia is in the initial markets, so treat availability as unconfirmed before planning build effort around it.

A Hacker News thread (255 points, 105 comments) centers on a developer's X post describing their run-in with Google's Android Developer Verification Program: their personal Play Store account was closed for inactivity, they could not create a replacement Play Console account, and when they turned to shipping an APK via F-Droid they say they hit a $25 verification fee plus an identity check. The post also claims that even distributing to fewer than 20 users requires a verified payments profile and an answer to a question about publishing on Android. The article text is a truncated copy of that post, so the program mechanics are reported second-hand from one developer's experience, not from Google's own documentation.

Why: If you ship or plan to ship an Android APK outside the Play Store — including dev builds handed to a handful of friends or testers — do not assume sideloading stays free and anonymous; per this account, the verification gate, the $25 charge, and the payments-profile requirement apply even below 20 users. Two concrete decisions follow: verify the current rules on Google's own developer page before you plan a distribution route, and don't let an existing Play Console account sit inactive if you want to keep it, since this poster's account was closed and could not be restored. For solo and small-team builders here shipping to a global store, an ID-verification plus fee gate is extra friction worth budgeting time for — but treat the specifics as unverified until you read Google's terms directly.

A developer who bought 10 identical Android 6.0.1 phones (2GB RAM) for an SMS-gateway deployment describes being pushed off Google Play: their text editor Tabby was rejected with a screenshot of an unrelated NSFW app attached to the review, and the appeal was rejected without explanation. They note that repeat offenses can lead to full developer account deletion, so they stopped trying to 'debug' the review process and will ship games and tools via F-Droid and itch.io instead. They also reference an unspecified 'latest monopoly consolidating move' by Google without giving details.

Why: If you distribute on Play, this is a concrete argument for maintaining a second channel: the stated downside here is losing the entire developer account, not just one rejected app, which is why the author refused to re-submit and probe the review. There is also a hardware note for anyone building device fleets — Android 6.0.1 with 2GB RAM was sufficient for their SMS-gateway use case. Nothing in this piece is Malaysia- or SEA-specific; it is a general platform-risk account.