安卓版Chrome能否使用Chrome扩展？自定义图片下载应用实现咨询

Absolutely possible—though you’ll need to work around Android Chrome’s more restricted extension ecosystem compared to the desktop version. Let’s break down how to approach your core requirement: adding a download button to Google Images’ view mode that saves images to a user-specified folder.

Key Feasibility & Limitations First #

Android Chrome does support Manifest V3 extensions, but not all desktop APIs are available. The good news: the core pieces you need (injecting UI elements, handling downloads, storing user preferences) are all doable. The biggest hurdle is direct folder access—Android’s security model prevents extensions from writing to arbitrary folders without user consent.

Step-by-Step Implementation Plan #

1. Set Up the Extension Skeleton #

Start with a standard Manifest V3 structure, making sure to request the right permissions:

{
  "manifest_version": 3,
  "name": "Google Images Folder Downloader",
  "version": "1.0",
  "permissions": ["downloads", "storage", "activeTab"],
  "content_scripts": [
    {
      "matches": ["*://*.google.com/search?tbm=isch*"],
      "js": ["content.js"],
      "run_at": "document_idle"
    }
  ],
  "background": {
    "service_worker": "background.js"
  }
}

• matches targets Google Images search pages.
• downloads lets you trigger and manage downloads.
• storage saves the user’s chosen folder URI (more on this later).

2. Inject the Download Button into Google Images’ View Mode #

Google Images uses a dynamic modal when you click to view an image. You’ll need to:

• Use a MutationObserver in your content.js to watch for the modal loading.
• Once the modal is detected, insert your custom download button into the top-right corner (matching your desired UI).

Example snippet for content.js:

// Watch for the image view modal to appear
const observer = new MutationObserver((mutations) => {
  const imageModal = document.querySelector('[role="dialog"]'); // Adjust selector to match mobile DOM
  if (imageModal && !imageModal.querySelector('.custom-download-btn')) {
    // Create and inject the button
    const downloadBtn = document.createElement('button');
    downloadBtn.className = 'custom-download-btn';
    downloadBtn.innerHTML = '📥'; // Use an icon or text
    downloadBtn.style.position = 'absolute';
    downloadBtn.style.top = '10px';
    downloadBtn.style.right = '10px';
    downloadBtn.style.zIndex = '9999';
    
    downloadBtn.addEventListener('click', () => {
      const currentImage = imageModal.querySelector('img[src^="https://encrypted-tbn0.gstatic.com"]'); // Adjust selector
      if (currentImage) {
        // Send image URL to background script for download
        chrome.runtime.sendMessage({ action: 'downloadImage', url: currentImage.src });
      }
    });
    
    imageModal.appendChild(downloadBtn);
  }
});

observer.observe(document.body, { childList: true, subtree: true });

Note: You’ll need to inspect Google Images’ mobile DOM to get accurate selectors—they can change over time, so plan to update this as needed.

3. Handle Downloads to a Specific Folder #

Android Chrome’s downloads API can’t directly specify a folder path, but you can use the Storage Access Framework (SAF) to let the user pick a target folder, then reuse that permission for future downloads:

In background.js:

let targetFolderUri = null;

// Load saved folder URI on startup
chrome.storage.local.get('targetFolder', (data) => {
  if (data.targetFolder) {
    targetFolderUri = data.targetFolder;
  }
});

// Listen for download requests from content script
chrome.runtime.onMessage.addListener((request, sender, sendResponse) => {
  if (request.action === 'downloadImage') {
    if (!targetFolderUri) {
      // Ask user to select a folder via SAF
      // Note: For full SAF integration, you might need a hidden extension tab to launch the file picker
      // Once selected, save the URI to chrome.storage.local
      chrome.storage.local.set({ targetFolder: userSelectedUri });
    } else {
      // Trigger download with the saved folder context
      chrome.downloads.download({
        url: request.url,
        filename: `${targetFolderUri}/image-${Date.now()}.jpg`, // Adjust filename logic
        conflictAction: 'uniquify'
      });
    }
  }
});

Important: The exact SAF integration might require a workaround (like opening a hidden extension tab that uses the FileSystemAccessAPI), since Chrome extensions on Android don’t have direct access to Android’s native file picker APIs. You’ll need to test and adjust this part based on current API support.

4. Test & Adapt for Mobile #

• Test your extension on Android Chrome directly (use chrome://extensions/ in mobile Chrome to load unpacked extensions, but note this requires enabling developer mode).
• Mobile Google Images has a different layout than desktop, so your content script selectors will need to be mobile-specific.

Alternative Workaround If Extension Limits Are Too Strict #

If the extension route feels too constrained, consider building an Android app using the Accessibility Service:

• The service can detect when the user is viewing a Google Image, overlay a custom download button, and use Android’s download manager to save to a specified folder.
• This approach gives you more control over file system access but requires writing native Android code (Kotlin/Java) instead of web tech.

Final Verdict #

Your goal is absolutely achievable with an Android Chrome extension—you just need to account for mobile-specific DOM structures and Android’s storage permission model. Start small: build the button injection first, then tackle the folder-specific download logic with SAF integration.

内容的提问来源于stack exchange，提问作者ax.falcon