0

In the Android developer guide, under Building an Audio App section, there is a statement:

The preferred architecture for an audio app is a client/server design. The player and its media session are implemented inside a MediaBrowserService, and the UI and media controller live inside an Android activity along with a MediaBrowser.

In the other hand, we have also the MediaPlayer class.

Which way is prefered in which situations?

Pushpendra
  • 2,791
  • 4
  • 26
  • 49
Piotr Aleksander Chmielowski
  • 5,640
  • 7
  • 29
  • 45
  • 1
    I would say the MediaPlayer is for the video, as in being something visual on the screen. This design from my perspective has the advantage of the service being in the background when the user will switch to other apps – petrumo May 18 '17 at 11:21

1 Answers1

2

Because such an architecture has multiple advantages mainly because there is a clear separation between the Ui which controls the music service and the music service itself. In this way music service can continue its music service irrespective of the type of the UI client. Different clients can get the active media controller from your Music service and show its own UI. Different apps can attach to your Music service (if you allow) & show different UI depending upon context, like Android Auto.

NIPHIN
  • 1,071
  • 1
  • 8
  • 16