I'm working on an app that allows the user to browse through a list of items. All of these items have a primary action (compose) and some of them also have a secondary action (search). As of now I'm using this structure:
However, I feel like it's not entirely clear what the primary action is or that there is one. This could be solved by adding an explicit button for the primary action, but this would result in a repetitive pattern of buttons. Plus it's usual for mobile applications to bind the primary action to the entire row.
Do any of you have a clever solution to this?