如何实现两个操作间的时间间隔统计？（例：应用充电启动到Button点击）

Hey David, great question! Tracking time gaps between specific user or app events like this is super useful for understanding user behavior, optimizing flows, or even debugging. Let’s break down how to implement this across the most common platforms—no fancy tools required, just straightforward code:

• First, when your app detects the charging start event (via the ACTION_POWER_CONNECTED broadcast), save the current timestamp to a persistent store like SharedPreferences (so it survives app backgrounding):

  // In your BroadcastReceiver or Activity that detects charging
  val chargingStartTime = System.currentTimeMillis()
  val prefs = getSharedPreferences("AppEventTimestamps", Context.MODE_PRIVATE)
  prefs.edit().putLong("charging_start", chargingStartTime).apply()
  

• Then, in your Button’s click listener, fetch that saved timestamp, calculate the difference from the current time, and use the interval as needed (log it, send to analytics, etc.):

  yourButton.setOnClickListener {
      val prefs = getSharedPreferences("AppEventTimestamps", Context.MODE_PRIVATE)
      val chargingStart = prefs.getLong("charging_start", 0)
      
      if (chargingStart != 0) {
          val currentTime = System.currentTimeMillis()
          val timeIntervalMs = currentTime - chargingStart
          // Convert to seconds if needed: timeIntervalMs / 1000
          Log.d("EventInterval", "Charging to button click: $timeIntervalMs ms")
          
          // Clean up the saved timestamp so it doesn't interfere with future sessions
          prefs.edit().remove("charging_start").apply()
      }
  }
  

• Start by setting up battery state monitoring to catch when charging begins, then save the start time to UserDefaults:

  // In your view controller or a dedicated analytics manager class
  func setupBatteryMonitoring() {
      UIDevice.current.isBatteryMonitoringEnabled = true
      NotificationCenter.default.addObserver(
          self,
          selector: #selector(handleChargingStart),
          name: UIDevice.batteryStateDidChangeNotification,
          object: nil
      )
  }
  
  @objc private func handleChargingStart() {
      let batteryState = UIDevice.current.batteryState
      if batteryState == .charging || batteryState == .full {
          let chargingStartTime = Date().timeIntervalSince1970 // Seconds since 1970
          UserDefaults.standard.set(chargingStartTime, forKey: "charging_start")
      }
  }
  

• In your Button’s IBAction, calculate the interval and act on it:

  @IBAction func onButtonTap(_ sender: UIButton) {
      guard let chargingStart = UserDefaults.standard.value(forKey: "charging_start") as? TimeInterval else {
          // No charging start timestamp found—handle this case (log, ignore, etc.)
          return
      }
      
      let currentTime = Date().timeIntervalSince1970
      let timeIntervalSec = currentTime - chargingStart
      print("Charging to button click: \(timeIntervalSec) seconds")
      
      // Clear the saved timestamp
      UserDefaults.standard.removeObject(forKey: "charging_start")
  }
  

• Use the Navigator.getBattery() API to detect charging start, then save the timestamp to localStorage:

  // Initialize battery monitoring
  navigator.getBattery().then(battery => {
      battery.addEventListener('chargingchange', () => {
          if (battery.charging) {
              localStorage.setItem('charging_start_time', Date.now().toString());
          }
      });
  });
  

• In your button’s click handler, compute the interval:

  document.getElementById('target-button').addEventListener('click', () => {
      const chargingStart = localStorage.getItem('charging_start_time');
      if (chargingStart) {
          const currentTime = Date.now();
          const timeIntervalMs = currentTime - parseInt(chargingStart);
          console.log(`Charging to button click: ${timeIntervalMs} ms`);
          
          // Clean up the stored timestamp
          localStorage.removeItem('charging_start_time');
      }
  });
  

• Edge Case Handling: Always check if the start timestamp exists before calculating—users might trigger the button without ever starting charging, so avoid errors from missing data.
• Storage Choice: Use persistent storage (like the examples above) if you need the timestamp to survive app restarts. For session-only tracking, just use an in-memory variable instead.
• Time Unit Consistency: Double-check whether your platform uses milliseconds or seconds for timestamps to avoid miscalculations.
• Analytics Integration: Instead of just logging, send this interval as a property with your analytics events (e.g., "button_click" event with "time_since_charging_start" as a parameter) to track trends over time.

内容的提问来源于stack exchange，提问作者David