newtophones07
1000+ Head-Fier
Like it or not, getting a decent MCU is one of the most challenging part of developing a modern DAP. There are two problems here, the obvious one is supply chain issue, a HiFi brand will need around 10K units of MCU to support one audiophile grade DAP products, a mobile phone brand will go for around 500K units for a regular mobile phone products, and will go well beyond 1000K unit with popular models. The reality is, without an established relationship with the semiconductors big-names, even getting a supply contract on outdated MCU is far more difficult that consumers can imagine.
The reason that semiconductor feels reluctant to work with small scale projects like DAP is because of the commitment of solution provider, and this is the second problem that stop us from using a modern MCU in DAP. The MCU is useless until there is a "solution provider" willing to take up the project and develop a "solution" for a particular application. You can imagine DAP is a niche market that is not particular attractive to the solution providers.
We expect the 1G RM + 32G internal memory will continue be the norm of sub-$400 Android DAP. The current N5ii can support upto 544GB (32+256+256) storage. Adding another 32GB to this will increase the maximum music storage by around 6% only, nothing really significant. N5ii uses eMMC as internal memory, its more expensive then TF cards in general, so we think it is more cost effective by keeping the cost of DAP down with 32G internal memory only and let users allocate the budget to the TF cards flexibly. At the end of the day, nothing comes free, its just a matter of paying for the eMMC internal memory upfront, or to get a bigger TF card when you really need the extra "few" GB.
I very much appreciate the response and detail. I look forward to the release, as I want to try a new device soon.