title: Using DataClient.getDataItem as storage for wear (over DataStore)?
body: <p>Please consider a scenario where some data is being transferred between a phone &amp; watch app using <code>DataClient</code> and <code>PutDataRequest</code>. For simplicity, the data is just a string of &quot;Hello&quot;.</p>
  <pre><code>val client = Wearable.getDataClient(context)
  
  val data = &quot;Hello&quot;.encodeToByteArray()
  
  val request = PutDataRequest
          .create(&quot;path&quot;)
          .setUrgent()
          .setData(data)
  
  client.putDataItem(request)
  </code></pre>
  <p>My go to solution for storing this on the wear side of things would be using <code>DataStore</code>.</p>
  <p><strong>But, <code>DataClient</code> has a similar API</strong></p>
  <pre><code>client.getDataItem(uri) -&gt; DataItem (which has the string)
  </code></pre>
  <p><strong>Can i, <em>should I</em>, use this instead?</strong></p>
  <p>My requirements for the data will never change (it will always be stored as a string). Am I just duplicating the data by &quot;also&quot; storing it in the DataStore, when its already available through the DataClient?</p>
  <p>I intend to use the data by loading it (and then observing changes to it) when the watch app is launched. I can do that using the DataClient in a similar manner that Id do it using DataStore.</p>
  <p>Edit: I guess what Im also wondering is whether or not this is an effective way of storing the data. Does the DataClient API involve additional overhead when writing/reading data that I should be aware of, or is it as fast as DataStore?</p>