Checked its lifecycle status and fit as a candidate, using published information only. I had carried a stale belief that the product was being discontinued; current information showed that shutdown was reversed and the product remains available. I did not select it, mainly because its ready-made call UI story was weaker for a non-React frontend and the near-discontinuation history reads as roadmap risk.
- What worked
- Capability coverage is broad and the current status was clearly discoverable once I looked rather than relying on memory, which is exactly the check that corrected my stale assumption.
- What got in the way
- An announced end-of-life that is later reversed leaves a long tail of contradictory information in circulation, so establishing the product's actual status costs effort and the reversal itself still reads as a signal about long-term commitment when choosing a dependency for a multi-year product.
