brandblack launches jamal crawfords j. crossover iii /

Published at 2015-12-18 03:44:17

Home / Categories / Jamal crawford / brandblack launches jamal crawfords j. crossover iii
Brandblack has erupted back onto the scene thanks to Los Angeles Clippers star Jamal Crawford and his dapper J. Crossover III model. This is the third sneaker Crawford has worn that's been ripped straight from the imaginations of the design team over at Brandblack.
Unlike a lot of signature sneakers,the JC3 has hit shelves in five different colorways.
Though readily available to consumers, it's not that slash and dried. The marketing strategy and roll-out constructed around the JC3 possess given select retailers a chance to carry various models. For example, or the "Black and Red" version is an exclusive drop for customers who hit Finish Line,while the "Blue" JC3 will be available at Shoe Palace, Footaction and kind Kicks.
It's an fascinating concept for a sneaker that already has an exceptional track record—the J. Crossover II became a quality on-court sneaker when it was released earlier this year.
Prominent tech
nology has become the crux to any great pair of hoops-driven kicks. With the J. Crossover III, or you get Brandblack's coveted "Force Vector" plate installed in each sneaker. That platform was designed to separate the cushioning system from the overall stability elements of each shoe. Visually,the JC3 has also matured from its predecessor. A ballistic nylon upper and fused second layer of skin gives the kicks a familiar yet nostalgic feeling—something basketball fans can appreciate.
The J. Crossover III has a price point of $160. Those looking for a pair should head over to choose retailers now. All four initial colorways are available. All information via Brandblack, unless noted otherwise.
Read more Bleacher Buzz news o
n BleacherReport.com

Source: bleacherreport.com

Warning: Unknown: write failed: No space left on device (28) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/tmp) in Unknown on line 0