Completed features, data sources, and privacy boundaries in one place. Versions v0.5.11–v0.5.14 strengthen precision, localization, local-data management, and report range control.
Latest functionality versionv0.5.14
Verified in the desktop-loaded build · Chrome Web Store public version remains v0.5.10
Complete local backup, favorite refresh, and report range control
Saved analysis data, refresh workflows, and the reporting scope are more complete while data stays processed locally in the browser.
Backup and restore now include normalized Instagram and TikTok post cache, analysis metadata, favorites, snapshots, comparisons, and Instagram recommendations, while remaining compatible with older backups.
“Refresh data” for a favorite account passively loads Instagram profile and Reels pages in the background, or a TikTok profile page; it only organizes first-screen data the platform normally loads. Full scrolling analysis remains manual.
Both reports add an eight-option analysis range below the data-information row, using four day and four post presets from Settings. Changing it updates only the eight KPI cards and engagement trend; the overview, top content, per-post details, and Excel retain their existing data sources.
Local datav0.5.13
A local data-usage overview in Settings
The Data section now includes a read-only storage dashboard so you can see what the extension has saved and the approximate amount of local space it uses.
Shows estimated IndexedDB and chrome.storage.local usage, browser quota, and storage-entry count.
Separately counts Instagram and TikTok accounts, posts, snapshots, favorites, and comparisons; Instagram also shows recommendation records.
Refreshes manually and never writes, clears, or changes existing data while measuring.
Localizationv0.5.12
Chrome-native extension localization
Chrome i18n metadata now supports Traditional Chinese, Simplified Chinese, and English. The extension name, description, and toolbar hint follow Chrome’s UI language while the in-extension language picker remains available.
Data precisionv0.5.11
Keep and display exact follower counts
When an already-loaded Instagram response contains follower_count, the extension retains that exact integer. Visible DOM abbreviations such as “1.1K” can no longer overwrite it; the panel and report can show the full number.
Chrome Web Store public versionv0.5.10
Passive capture fix for similar Instagram accounts
Instagram may return similar-account JSON as text/javascript. This release updates the existing response detection and, when no local cache exists, opens Instagram’s normal similar-accounts route so the platform loads the data itself.
Only stores the account, name, avatar, verification, and relationship status that Instagram actually returns.
Does not infer similarity scores, follower counts, ER, or views; missing platform data remains empty.
Does not create or replay GraphQL requests.
Featurev0.5.9
Similar creator lists for Instagram
The Instagram panel gains an Analytics / Suggested creators switch. Recommendation data is stored separately on-device and never enters post analytics, snapshots, comparison, or export.
Experiencev0.5.8–0.5.7
Favorites, metrics, and interface details
Adds panel shortcuts for favorites, Instagram and TikTok filters, two-decimal rounding for ER/ERR under 1%, and clearer cursor behavior across Favorites and Settings.
Settings and managementv0.5.6–0.5.5
Settings, backup, and favorite accounts
Introduces a versioned SettingsManager, configurable analysis and report ranges, KPI order, top-content preferences, snapshot policy, cache limits, backup/restore, and a favorite-accounts page.
Export filenames can use platform, account, date, and analysis-range variables.
Reducing the cache limit trims local records immediately.
Resetting settings preserves saved snapshots and analysis cache.
Data completenessv0.5.4–0.5.2
First-screen Reels, collaboration posts, and profile fallback
Improves Instagram first-screen state capture, Reel dates and thumbnails, collaboration posts, total media count, and follower fallbacks, with matching platform and collaboration marks in the panel and reports.
Product mergev0.5.0
Instagram and TikTok in one extension
“Social Analytics | Passive Analytics” unifies the brand and entry points. The two platforms still use separate parsers, databases, reports, history, and comparison data so their content fields and metrics stay distinct.
Brand and first-screen datav0.4.4–0.4.3
A clearer Instagram icon and first-screen Reel fallbacks
Updates the Instagram-specific toolbar icon and moves the existing passive observer to the MAIN world at document_start, reducing the chance that the newest first-screen Reels miss their date before the page state is complete.
Does not create or replay Instagram requests.
Only supplements fields from responses, page state, and visible content Instagram has already loaded.
Reel data completenessv0.4.2–0.4.1
Do not end analysis early for Reels missing a date
Reels without a date in older cache are no longer treated as fully collected. Analysis keeps waiting for complete platform-loaded data and merges a delayed taken_at by shortcode.
History and comparisonv0.4.0
Snapshots, historical trends, and multi-account comparison
Completed analyses can be saved as local snapshots and viewed as trends. The account library and comparison page use existing cache or snapshots to compare accounts on the same platform, with CSV, JSON, Excel, and PDF export.
Snapshots and comparisons reuse the same metrics, medians, and posting-frequency calculations.
Data stays in the browser; no backend was added.
Reel data fixesv0.3.3–0.3.0
Strengthen passive handling of first-screen Instagram Reels
Builds on the existing Instagram post and Reel analysis by improving first-screen state and publication-date timing. It supplements available fields from page state already loaded and corrects posting-frequency calculation for post-count ranges.
Fields Instagram does not provide remain N/A; they are never filled by inference.
Reports and data precisionv0.2.9–0.2.1
Detailed reports across five ranges, with data fallbacks
Adds a standalone detailed report that recalculates 7, 14, and 30 days plus the last 10 and 30 posts independently, with trend charts, top content, per-post details, browser PDF printing, and Excel export.
Posts per week for post-count ranges uses the actual publishing-date span; a single post remains N/A.
Improves avatar, thumbnail, pinned-post, cross-profile/Reels merge, days-since-publishing, view-median, and ER display behavior.
Adds Traditional Chinese, Simplified Chinese, and English with automatic language detection and manual switching, plus a linked company logo.
High-density controlsv0.1.10–0.1.5
A collapsible, draggable in-page analysis panel
Turns the analysis interface into a local panel that appears only on Instagram profiles, then increases information density and flexibility: collapse it, drag its position, resize its height, and retain that state without disrupting scan, export, or cache behavior.
Adds Chinese metric help, the brand logo, posts per week, latest-publishing date, content-type signals, and guidance when view data is missing.
Adds average likes, comments, and views, a view median, and publication dates for top posts while keeping compact, readable number formatting.
Initial usable releasesv0.1.4–0.1.0
Local passive observation and the Instagram analysis foundation
Builds a Manifest V3 in-page tool that passively observes fetch/XHR responses Instagram already made, parses only required post fields, keeps a local IndexedDB cache, and offers start, stop, range selection, top posts, and CSV/JSON export.
Early patches cover Reel/video views, retaining data while switching between posts and Reels, DOM fallbacks, and stopping scroll cleanly. It has no backend, stores no credentials, and never initiates Instagram private API calls.
How should you read these version labels?
Chrome Web Store public version means the version installable from the Store today. Latest functionality version means a completed update that has been verified in the desktop-loaded build and will be included in a later Store submission. Available values always depend on what the platform has actually loaded.