Sources & Verification Standards
Why this page exists
The most common failure in a knowledge base is not writing too little — it is treating what we cannot measure as non-existent, and writing inference as fact. So we publish our information sources and verification methods in full, so you can re-check every one of our conclusions on that basis.
Source grading
| Grade | Definition | Example in this knowledge base | How it is labelled | |
|---|---|---|---|---|
| **A | First-hand official** | Official APIs, official documentation, original text on official pages | Version/build/developer/publish date returned by the App Store API; original wording from the official site | Stated directly |
| **B | Measured and reproducible** | We visited or ran it ourselves and recorded the result | Vendor backend returning HTTP 200; reachability tests for each platform | Measurement evidence attached |
| **C | Public second-hand** | Media reports, industry self-media, platform page summaries | Market-size figures; number of factories | Source cited + reliability warning |
| **D | Inference by this team** | Reasonable deduction based on facts | Inferred partnership workflow; interpretation of industry convention around Android distribution | Marked not published / to be verified |
Do not use Grade C or Grade D content directly for investment or contracting decisions. Go back to first-hand sources to verify.
Product information: what counts as authoritative
FeiEgg product parameters take these two sources as authoritative, and nothing else counts as a basis:
- The App Store official API (iTunes Search / Lookup)
Returns: app name, version number, release date, developer name, category, content rating, bundle size, number of ratings, original official description. This is structured data with no human editing, and is the most reliable.
- Original text on the official site www.feiegg.com
Used for the official statements of product positioning, feature list and partnership value proposition.
Things we deliberately did not do
| Not done | Reason |
|---|---|
| We do not state specific technical parameters (such as the number of simultaneously connected devices or the number of mode levels) | Neither the official site nor the App Store discloses them, so making them up would be fabricating |
| We do not state precise market-size figures | Second-hand citations are heavily distorted and the original source cannot be traced |
| We do not publish a "list of factories we work with" | Signing basis is required from both parties; we do not list anyone unsigned |
| We do not publish a list of hardware-compatible device models | No official list exists |
How industry data is verified
Where this knowledge base makes industry judgements, the sources are of these kinds:
| Source type | Use | Limitation |
|---|---|---|
| Public company lookups (legal entity, business scope) | Judging industrial-belt distribution, factory vs brand | Summaries may be pulled from the wrong page; company names and contact details must be verified against the business-registration system |
| National Enterprise Credit Information Publicity System | Verifying whether an entity is real | Requires manual lookup |
| B2B platform certification badges (e.g. "manufacturer") | Judging whether production capacity genuinely exists | The platform's verification standard is not public |
| Industry self-media and white papers | Understanding trends and practitioner views | Second-hand; figures require caution |
A special note on company information: Company summaries returned by search engines frequently mix information about different entities together. In our own testing we encountered cases such as "the company is registered in Dongguan, but the phone number in the summary belongs to Jiangsu". This knowledge base therefore does not provide a list of company contact details — for anything involving a business contact, please verify it through official channels first.
Known limitations
An honest account of what we cannot do:
| Limitation | Explanation |
|---|---|
| Some product information cannot be published | Pricing model, data granularity, SDK technical details and similar are commercial terms not disclosed on the official site |
| We cannot verify the status of partners | This knowledge base does not publish partnerships that have not been confirmed by contract |
| Industry figures have limited precision | This category lacks authoritative official statistics; most figures are estimates by institutions or citations from self-media |
| Content updates rely on manual work | After a product version update, this knowledge base may lag; please treat the official site and the App Store as authoritative |
Suggested checks
If you intend to make a decision based on this knowledge base, we suggest:
- Product parameters → open the App Store page and the official site and check them yourself
- Qualification numbers → verify at the MIIT filing system / the National Internet Security Management Service Platform
- Market figures → find first-hand reports from institutions such as iiMedia Research or Euromonitor
- Partnership matters → always take the contract text as authoritative; no verbal or page statement counts