Skip to content

Paul “ED” Edworthy

My feedback

1 result found

  1. 20 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  General  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Hi there! I don’t have an Android Wear, so I have no idea how that stuff works. If you could explain it very thorough, I may have a chance, otherwise, I’ll just have to wait until I buy an Android Wear (if I ever do).

    An error occurred while saving the comment
    Paul “ED” Edworthy commented  · 

    Hi Erlend, thanks for responding, your work on this app is great and no other MediaMonkey remote comes close. I'll help explain as best I can, but I'm a designer, not a developer, so apologies if it's not technical enough.

    How I understand it, implementing Android Wear (AW) support is supposed to be relatively easy, referencing an api here and there to pass over a value/action and AW does the rest.

    From the users perspective, AW mirrors the Notification Panel that you find on an Android device. Every notification that pops up, will also be displayed on an AW device (unless blocked by the user). I'm guessing that since your app is a media controller, you must declare it as such in order for the play/pause features to work on the interactive notification. AW recognises this and creates an appropriate visual notification/card to display on the watch.

    In general, each notification card can be swiped up or down to display the next or previous card, and each card can be tapped for a specific function. In this case, it shows the currently playing song and when tapped, it pauses/plays the song.

    From there, each notification can be swiped to the right to dismiss it, (unless it's a perminent notification). If you swipe to the left, you can access additional functions, the last always being "Open on phone" and "Block app". These additional functions can come in several forms, like a bit of information that when tapped can alternate extra information, (e.g. daily steps and weekly steps, this could be used for lyrics and song info).

    The standard format for a media player however is that the screen is split into 4 quaters (imagine an "X") and each quarter is a button. Top = volume up, bottom = volume down, left = previous track, right = next track. With your app, most of this is already done, except the buttons don't do anything, so it may be as simple as assigning the correct action to the correct button.

    Let me know if you need anything else.

    Paul “ED” Edworthy shared this idea  · 

Feedback and Knowledge Base