About these guides
Editorial standards, evidence and corrections
Our guides help creators plan clearer mobile video and understand where VidFuego fits. They are published by Irondale Village, Inc., the publisher of VidFuego, and promote the app.
Standards updated .
Product facts and compatibility
VidFuego guidance should match its implemented features and approved product information. Native iPhone Camera settings, third-party capture tools and VidFuego controls are different workflows. Device support, recording mode and plan limits matter; a successful example on one setup does not establish universal compatibility.
Use the current feature overview, plan comparison and support information alongside a rehearsal on your actual devices. Android availability remains coming soon. Capture quality and fused-export quality are separate considerations.
Sources and their limits
Where a guide lists sources, the links identify relevant product documentation, official guidance or other references. A source link is useful only if it supports the claim being made. A reachable URL, a citation count or a structured-data check does not establish the accuracy or completeness of an article.
Some practical guides do not yet include citations or original demonstrations. The library's technical checks cover page construction, links and consistency; they do not replace a claim-by-claim editorial review. Time-sensitive platform, device, legal and business details need current verification appropriate to the question.
What counts as demonstration evidence
An actual test or case study should identify the app version, device models, operating systems, plan, relevant accessories, environment and observed result. It should explain limitations and provide the real sample or recording when available. A planning diagram or checklist is useful preparation, but it is not a measured device test.
- Examples should distinguish proposed steps from observed results.
- Performance claims should state how the result was measured and what it applies to.
- Supplied media and identifiable participants need an appropriate permission basis.
- Reviews, qualifications and customer outcomes should never be invented.
Publication dates and revisions
Publication dates identify the initial guide release. Updated dates identify substantive revisions recorded for that guide; they are not a promise that every external source was checked on that date. Shared navigation or styling changes do not by themselves refresh every article's factual-review date.
When app behavior or source guidance changes, the affected explanation and product claims need review. Significant corrections should describe what changed, with a revision date that reflects the actual work.
Record your own evidence
Use these blank worksheets to document a real rehearsal or a comparison. Enter what you actually observed, retain the sample files and keep untested conditions explicit.
Report an error or request clarification
Use the support contact form to report a guide problem. Include the page URL, the statement in question and an authoritative reference or reproducible observation when you have one. For a device issue, include the app and OS versions, device model and steps needed to reproduce it. Avoid sending passwords or other sensitive account information.
A report is a request for review, not confirmation that a correction has already happened. We do not promise a response deadline or add a reviewer identity until that review actually occurs.
Put advice to a practical test
Start with a short recording, review picture and sound, and finish a representative export before a longer session. Browse the creator guides or choose a creator workflow to find a suitable starting point.