It should offer the option of playing alongside Push 2, or at least it should definitely offer the option of using multiple Push 3 devices on the same account, in the same Live project.
Why?
This strategy will give you huge benefits. Push 3 could be modular, in the sense of - you could play multiple Push 3s at the same time. Obviously this will result in a better workflow for everyone with limitless possibilities, and the chance for Ableton to sell more than one Push 3 for each customer.
If you look at what Roli did with the Roli blocks, that could be the same for Push 3. Imagine the opportunities when the hardware is modular and endlessly composable of multiple Push units. Now THAT is what I would call Push 3
TLDR - my idea (that will obviously increase the fun for me and increase your sales) is twofold: when u release Push3, a) either allow Push2 and Push 3 to play together, or b) make Push 3 itself modular and composable like Roli Blocks - this way, one customer might buy an endless amount of "Push 3 blocks" to compose his desired Push3 workflow, according to personal taste and production style. Some hiphop artists would have their own setup of Push3 blocks, some rock artists different Push3 blocks setups.
But still, why?
Well I will give you my use case:
As a developer I was super excited when I discovered that these options exist:
Programmatic access to Push made available by Ableton:
- https://github.com/Ableton/push-interface
Communication between Push and the Juce C++ framework:
- https://github.com/Ableton/push2-display-with-juce
I want to be able to deeply customise Push with the libraries above (through Juce specifically) but I want to use the created software ALONGSIDE the regular Push. Essentially, my desired ideal workflow would be:
A regular Push , communicating with one or more customised Push'es. There can never be enough Push'es. And Live should allow communication to/from multiple Push devices, to be truly modular.
Cheers