Setup guide · Demo access · Screenshots · Visual customization

Release checks — edition v06

13 October 2026 · Mobile 1.28.1+29 · Flutter admin 1.1.0+2

Current correctionEvidence / scope
ListingPrepared a title with a pipe separator and capitalized With, removed trademark-sensitive/redundant tags, removed review-status updates from the description, repaired the Skype anchor, and corrected the old v1.22 date using the recorded marketplace approval date of 25 November 2023.
Demo APKA separate universal Android APK compiled on Flutter 3.41.4 / Dart 3.11.1. Package com.certainity.simpleworld.demo, version 1.28.1+29, minimum Android SDK 24 / target 36. APK signature verification passed. This demo uses a test signing key and has no Internet permission; it contains synthetic Firebase SDK configuration, local fictional records and no live author credentials.
Demo access and screensEntered demo@simpleworld.local / Demouser in the final APK on emulator-5554. Sign-in opened the sample Home. Home, Discover, Profile, Chats and Menu were captured alongside the initial sign-in screen. No fresh physical-device or connected-backend acceptance is claimed by this sample check.
Admin previewThe buyer Flutter read-only public_demo.dart entry point compiled successfully. Chrome displayed Overview, Users, Posts and Reported posts; all four were captured. The entry point does not initialize Firebase and does not perform administrative writes.
DocumentationTen main-screen captures are included, plus a visual logo/name/color guide, demo instructions, a reproducible separate sample-build helper and external service-cost information.
Native configurationReplaced the incorrect token-shaped notification-channel value with simpleworld_default, matching the notification service. Corrected the source Android Internet permission spelling. Removed obsolete trademark wording from the admin web manifest.

Remaining installation-specific acceptance

Configure your own Firebase project and deploy the complete supplied backend before connected use. The author's strict live database-rule cutover still requires a compatible Android/web client rollout. Complete signed-in app/admin acceptance in your installation. iOS source has no completed Mac/Xcode build or iPhone acceptance record. Purchases are disabled. Marketplace approval is independent of these checks.

Historical v05 checks — 4 October 2026

Setup guide · Local connected demo

Release checks - buyer candidate v05

4 October 2026 · Mobile 1.28.1+29 · Admin 1.1.0+2

Combined source review candidate. CodeCanyon submission has not been completed. Seven missing client functions are now active in the author's review installation. Strict live database rules require a compatible client rollout.
CheckEvidence
Android releaseSigned APK compiled. Signature, non-debuggable flag, ZIP and all nine native-library 16 KB alignments passed. APK code/assets match the previously emulator-verified build. Store signing/version acceptance remains separate.
Earlier live emulator checksHome, distinct public profile photos, profile covers/bios/posts, comments, story playback and three video posts were checked against the refreshed hosted fictional community.
Physical AndroidThe author reported sign-in, uploads and notifications passed on 4 October 2026. Device model and raw test records were not supplied. Group/report/moderation/account-deletion workflows have not received a new signed-in acceptance run after the function deployment.
Current source analysisFresh credential-free copies of both current buyer projects passed flutter analyze --no-pub lib test with no issues on 4 October 2026. Analyzed lib/test files and lockfiles matched the buyer source hashes. No new unit tests were run for this packaging refresh.
Client function deploymentcommunityAcknowledgeNotice, communityActivity, communityCredits, communityDelete, communityGroup, communityGroupReport and communityReport were deployed selectively and read back as ACTIVE on Node.js 22. Each rejected an unsigned empty request with HTTP 401 / UNAUTHENTICATED. The eight existing function hashes were preserved. This verifies deployment and authentication rejection, not complete signed-in behavior.
Live security cutoverNo strict Firestore rules, Storage rules or Hosting deployment was performed with these function additions. Confirm compatible Android/web client rollout before the coordinated strict-rule cutover. Buyers deploy the supplied complete backend into their own project.
Source refreshMobile chat/group compatibility helpers, directory/story fixes, the matching backend public-group module and Firestore rules are included. The v04 admin interface source and licensed media are preserved.
PackagingStatic exclusion and per-file archive hash checks are recorded in the package manifest and private preparation report. Dependencies, credentials, private customer data and known generated preview media are excluded.
Admin and earlier backend QAPreserved v04 evidence is reproduced below. It is not a claim that those tests were rerun after this source refresh.
iOSSource and Mac verification helper are included. No Mac compile or iPhone acceptance has been performed.

Remaining release work

  1. Confirm compatible Android/web client rollout, coordinate strict live database rules and complete signed-in app/admin acceptance.
  2. Match screenshots and listing metadata to v05 and the exact supported feature scope.
  3. Complete connected admin acceptance and iOS verification before advertising those paths as production tested.
  4. Complete the existing item's update workflow and verify the marketplace review status.

Generated art

Hosted fictional photos are preview content. They are not inside this download. See Envato's AI-content policy. Buyers supply their own Firebase media.

Preserved v04 verification history (3 October 2026)

Setup guide · Connected mobile quick test

Release checks — buyer candidate v04

3 October 2026 · Windows local verification

Status: buyer review candidate with local Android, backend and public interface checks. The original production security cutover, connected public reviewer hosting, iOS/Xcode, physical-device acceptance and marketplace submission remain pending.
CheckResultScope
Flutter analysisBoth projects passedflutter analyze --no-pub lib test; no issues. Flutter 3.41.4 and Dart 3.11.1.
Flutter tests14 passed across the preserved mobile and updated admin sources8 mobile tests: shell, login, splash and five buyer demo/media/draft/render checks. 4 admin UTC/date/empty-chart tests plus 2 read-only public-preview navigation/report/search tests at 390 and 1440 pixels. The unchanged mobile source retains its v03 checks; all 6 admin tests were rerun for v04.
Backend checks46 passed16 permissions/moderation/cleanup, 6 timeline/expiry, 8 earned-credit checks, 10 mobile boundary checks and 6 review regressions. Node 22.23.3, isolated fictional emulators only. Direct-handler expiry checks do not prove production scheduling.
Attack and compatibility regressionsPassedNo-token and genuine anonymous mutations denied; private profiles and protected credits/roles denied; custom UID collision reads/queries denied; spoofed message identities denied; Unicode names stay valid; oversized public fields cannot expand into an unwritable projection; ordinary and delayed unfollow cleanup preserve the intended notices.
Native Android checksFocused emulator checks passedSeparate application ID and isolated backend. Email sign-in, cached home, discovery, public prefix search across older profiles, foreign public profile, follow/unfollow, existing chat stream and two real mobile SDK transaction sends. REST concurrent payload tests separately preserve unread counts. Not complete physical-device, OAuth, push, camera/video/PDF, ads or store acceptance.
Android compilationAPI 36 debug and release APKs builtFictional configuration, separate test package ID and a disposable test signing key in a private QA copy. No test configuration, key or binary is included in the buyer ZIP. Native Java 8 deprecation warnings remain. Release APK was compiled with a disposable test key. The v04 continuation built release mode with the exact isolated emulator project and ports, then re-signed the private QA copy with the QA debug certificate to retain its test installation. A private manifest override permits local HTTP for Firebase emulators; the buyer release manifest keeps HTTPS defaults. Two mobile SDK transaction messages committed and the recipient unread count increased from 6 to 8. Buyer production signing remains separate.
Native APK format9 libraries passedOffline ELF load-segment and uncompressed ZIP alignment checks on the test-key release APK. The owned emulator reports PAGE_SIZE=16384 and renders release Home, directory, prefix search and chat. The QA certificate and ZIP 16 KB alignment were checked after re-signing; the release app has no DEBUGGABLE flag. No AAB metadata, physical-device or Google Play acceptance claim.
Admin web6 tests and fictional-preview release build passedThe connected admin entrypoint retains the prior browser review. The added public_demo.dart entrypoint never initializes Firebase. All 6 admin tests and analysis passed. Browser review covered record search, disabled profile/report details, phone navigation at 390 x 844 and the desktop layout. No browser warning/error logs were reported in this local preview session. JavaScript build used; WebAssembly dry-run warnings remain.
Buyer media and fonts19 licensed PNGs retained; 39 local fonts recordedLicensed PNGs preserve the v01 verified hashes and real alpha. Font notices and mobile-fonts.json are included. 35 known generated original media hashes were compared and excluded from the buyer source.
Quick setup helperPassedCreates a fictional Android configuration in a fresh copy; refuses overwrite and preserves its file hash after a second invocation.
Paid productsDisabledUnavailable in the running app. Unverified developer example retained outside lib. Purchases and restoration are excluded from supported claims.
Buyer archivePer-file manifest includedPackaging checks exclude private configuration/signing material, dependencies, build output and known generated preview media; every manifest entry is read back and checked against SHA-256.

Public review links

Matching English guide · Read-only fictional admin preview. This frontend preview demonstrates no live backend writes. The connected isolated demo destination is still undecided.

Remaining release work

  1. Select a separate Firebase/Hosting destination for a publicly accessible connected fictional demonstration. The included public interface preview stays read only and the English guide is hosted separately.
  2. For an existing installation, preserve backups and verify restoration, resolve legacy group ownership and shared media, prepare compatible signed client updates, then apply and verify the coordinated security cutover. The author completed a private document/media backup and isolated local restore drill. Auth account export is retained separately; Auth sign-in restoration and hash parameters, cloud restoration, verified legacy ownership and compatible production client rollout remain pending. Creating this candidate did not deploy rules or alter customer data.
  3. On a Mac, run tools/verify-ios.sh after configuring Xcode/Firebase. Complete signed iPhone checks before advertising verified iOS support.
  4. Finish physical Android and configuration-dependent OAuth/APNs, media, ads and notification acceptance in your own installation.
  5. Review metadata, screenshots, rights and support details before marketplace submission. Acceptance remains the marketplace's decision.

Source tests and setup helpers are included. The local sample is fictional. New on-device draft/archive/search/demo notices remain local features; the quick-test guide distinguishes those from connected Firebase workflows.