We really want to work with Nordic, but they makes it hard.

[Bndit]

It seems like a really great company, but after exploring and asking , and searching for a good BLE solution, I just can't find a good fit.

So you want a GOOD processor, and BLE . If you go with the nrf8001 and external MCU you get a pretty old BLE solution, nobody knows if its going to be here next year, AND it requires so many components around it including 2 crystals, which summed up to a price of a BLE module ( around 6$)

If you go with the more advanced solutions such as nrf51 series, you find out that the processors are just there to say : hey we have an ARM inside.

1. No DAC option ( any new ARM has it)
2. No RTC
3. No flash emulator to save stuff between resets / eeprom.

and the list is pretty long, and thats not including long development time.

This is not a rant, quite the opposite, it seems like a great company (and its not from China/ Thailand or whatever) , but every solution you check has at least 1 huge drawback .

Am I completely wrong here ?

[endnode]

Your summary for nRF51 seems to be inaccurate, can you elaborate with some examples what you lack in points 1/2/3 and which competition can offer it? Chip has many HW peripherals, has RTC and TIMER (several of them) and has 256kB of flash. Also why you don't consider nRF52 which is more power effective, has more flash/RAM/peripherals and cost difference is small? To be honest I haven't met better low-power Bluetooth processor on the market, can you hint what can give you more then nRF52?

[endnode]

When it comes to nRF52 hardware features you don't need to seek here, just read it on-line in Nordic Infocenter. When it comes to SDK and "libraries", I can only say that there seems to be examples for all peripherals and also some useful modules, I had always faster development time with nRF5x then with STMicro SDKs for STM32 family, but that's very individual. If you are going to develop the code, you need to download the SDK and dive into it. If you are not the developer, then ask your dev. team to conduct proper feasibility. You seems to be pretty rushing and counting every day of development effort but isn't it even more risky to ask random folks on the internet "how easy is it to develop something with certain platform"?