Available should mean a user can actually reach it
When Srithongkwao describes a web experience as available, the public destination should load and provide the stated experience. When an Android download is presented, the link should point to the intended application or store destination. A product should not be marketed as complete merely because a design, prototype or internal build exists.
Development work is described separately
Products can spend a long time in development, closed testing or technical preparation. Those states are normal, but they are different from public availability. Srithongkwao's public website separates current products from work that is still being built so visitors can understand what they can use today.
Web and Android are different delivery channels
A product may offer a browser experience, an Android application or both. The two versions can share a purpose without being technically identical. Permissions, installation, offline behavior and release timing can differ. Product pages therefore describe the available channel rather than assuming one platform represents every other platform.
Feature limitations are part of the product description
Trust improves when a product states what it does not do. Fortune results are belief-based entertainment rather than scientific or professional determinations. Weather information supports everyday understanding but does not replace official emergency warnings. APP Tester supports testing workflows but is not an official Google product. These limitations are not fine print; they help users choose the correct tool for a task.
Public policies should be easy to find
Privacy, Terms, Help and Contact pages are linked from the main website. Product-specific policies are linked where a product processes different kinds of information, such as uploaded images. A user should not need to discover an important policy only after granting a permission.
Why stale wording matters
A live product described as preparing is confusing. An unavailable product described as ready is worse. Public pages should be maintained as product status changes. Srithongkwao treats status text as product information, not decoration, and updates it when live behavior changes.
What visitors can verify themselves
- Open the product destination linked from the official Srithongkwao domain.
- Review the product description and its stated limitations.
- Read Privacy and Terms before sharing personal information.
- Use the Help and Contact pages when public information does not answer a question.
- For Android distribution, verify the app identity and developer information shown by the distribution channel.
Why we publish this guide
A digital brand earns trust through consistent public information. Explaining how status is described makes it easier for users, reviewers and partners to distinguish a real service from a placeholder. It also creates a record of the standard Srithongkwao intends to apply as more products are released.
