iotnews

Top Factors to Consider when Selecting a DevKit – Part II

Blog Post created by iotnews Employee on Oct 17, 2017

By Joe Cozzarelli (joecozz), IoT Business Development Manager at Verizon

 

 

(Note: this is the second of two posts about Selecting a DevKit. For the first, click here.)

 

When it comes time to develop your new IoT solution, you’re going to want to start from a strategic place that enables you to get to revenue with efficiency and scale. A hardware development kit, or DevKit, is a tool that will help you show a proof-of-concept before going to production on a solution. A good DevKit requires a particular set of characteristics to help you stay on the path to revenue and scale. Our four critical factors are:

 

  • Ecosystem Flexibility
  • Microcontroller Selection
  • Connectivity Selection
  • Open Development

 

In an earlier post, I dug into the power of ecosystem flexibility and microcontroller selection; let’s get into what connectivity selection and what open development can mean for your next project.

 

Getting device data to your platform is critical to building your IoT solution. A big part of that is selecting the right Connectivity model to maximize performance characteristics like battery life and coverage. That’s why connectivity must be part of the conversation during the earliest phases of design. With the advent of new connectivity types such as LTE CAT-1, LTE CAT-M1and NB-IoT, there are more features and capabilities than ever for developers to draw from when designing a solution and at the same time, many questions that need to be answered before making a decision. For example, does the application use voice? How much data will be used in the application? A DevKit that easily supports a variety of connectivity types is the most direct way to evaluate and ultimately select the right type of connectivity for your application.

 

To help you begin your next solution on the right foot, our DevKits have been pre-selected for common IoT use cases while keeping connectivity options in mind. That can mean design efficiency, profitability, and scalability of the final product. And that leads to successful implementations.

 

ThingSpace, Verizon’s IoT platform, operates on the Verizon Open Development environment, where designers can find certified devices and modules. Every device that operates on the Verizon wireless network must be certified. Some OEMs choose to use a Chip Down design strategy which requires a deep RF bench. To simplify the design process, component OEMs have created a wide variety of modules that integrate basic radio elements (baseband, transceiver and power management) as well as other salient features into easy-to-use design elements. These modules can be certified as elements and, when integrated into devices, reduce the time to certify a device significantly.  There are also fully certified devices that have been tested and are ready to go. Coming soon to the Open Development environment will be ThingSpace Ready modules and devices which will be tested to support the ThingSpace SDK, allowing easy access to ThingSpace and its features.

 

Inside the Verizon ThingSpace community at thingspace.verizon.com, you’ll have a unique opportunity to get involved with the Verizon partnership ecosystem.

 

Members of the community can:

  • Share ideas, challenges, and inspiration with your peers
  • Communicate with Verizon to chat with subject matter experts
  • Read the latest news and information related to ThingSpace updates and developer events

 

To get into the ecosystem, and see how Verizon can help with your next development project, join the ThingSpace community today.

Outcomes