design patterns – Explicit vs Implicit save. Differences between the expectations of Android and iOS

Our application makes use of a metaphor of type & # 39; Shopping Cart & # 39 ;, in which users can select from a variety of items and then confirm or delete all these items at once. We will call this explicitly save.

The problem is that when we tested on an Android user, this pattern seemed strange and the behavior of removing all the elements by pressing the & # 39;XIt was jarring. His assumption was that when selecting an article, it would be saved implicitly, and that the & # 39;X& # 39; button would effectively have the same behavior as the & # 39;Factbutton & # 39;

Is this a commonly expected behavior on Android? (I'm an iOS user)
And if so, is it horribly jarring to maintain this behavior?

EDIT: The question focuses more on the behavior of the top left navigation button. When a user presses this button, they return to the application's home screen. The question is: When this button is pressed, are you expected to confirm the changes made to the card or be discarded?

Sketch

Download the bmml font – Wireframes created with Balsamiq Mockups

Some notes about this drill:

1) The search bar and autocomplete suggestions appear as an enlarged section at the top of the cart screen.

2) As the search bar expands and shrinks to show the Cart, the & # 39;XThe & # 39; button is the same element of the user interface all the time (to try to eliminate confusion about where you will navigate)

3) Users have the ability to remove items from the cart directly from the list.

4) This is not really a shopping app. There is no exchange of money when I press & # 39;Fact& # 39; Think of this as putting together a list of things that I did today, and & # 39;Fact& # 39; gives me feedback on the things I did.