Categories
Hackster.io

Nordic nRF9160 DK // Unboxing

We check out this cool kit from Nordic: a multi-sensor cellular IoT prototyping platform for hardware engineers. Easily connect Arduino shields and standalone sensors to the nRF Connect for Cloud platform (nrfcloud.com).

Where the Thingy:91 device (previously: https://www.youtube.com/watch?v=tLUKgDT2V9g) comes with built-in sensors and a consumer-ready interface, the nRF9160 DK empowers you to prototype apps with your own custom hardware.

nRF9160 DK materials:
// https://www.nordicsemi.com/Software-and-tools/Development-Kits/nRF9160-DK
// https://www.nordicsemi.com/Products/Low-power-cellular-IoT/nRF9160

Thingy:91 materials:
// https://www.nordicsemi.com/Software-and-tools/Prototyping-platforms/Nordic-Thingy-91/
// https://www.hackster.io/glowascii/getting-started-with-the-nordic-thingy-91-mac-8d44e5

Categories
ProgrammableWeb

5 Tips to Build Developer-Friendly API Products

In a conversation with Thomas Bush at Nordic APIs, Rahul Dighe (Paypal’s API Product and Platform Product Leader) explains his theory on how great API products are built deliberately. This article elaborates on his ideas regarding the deliberate, rigorous process of building APIs with an intentional design for long-term use.

 Tip #1: A Thoughtfully Curated Developer Team

Rahul introduces a thought experiment outlining three types of developers who might use PayPal APIs: a newly matriculated freelancer, a payments expert with 10 years of experience in the field, and a distracted developer whose real interest is focused elsewhere. Each type of developer has their own level of experience and set of requirements. With this in mind, Rahul proposes that you “consider the usage patterns of your primary developer archetypes when building new APIs.”

Keeping this consideration in mind, it’s also important to remember that the API is not the end of a product design, rather it is a pathway to the end: the needs will vary from a company looking for a non-API widget for integration, right up to a company looking for a fully fleshed-out API solution.

The last element of this tip is to create a “one-pager.” Rahul advises teams to write up a brief document outlining all of the inputs and outputs, and core integration patterns the API will work to support. This document will serve as a kind of mini mission statement for the team to refer to throughout the design process. 

Tip # 2: Make Naming Your New Obsession

The name of the API will be an anchor the team works around for a long time. Rahul explains that “while you might be able to evolve quickly, there’s no guarantee your developers will too.” Bush refers back to an article he wrote on the same theme, “10+ Best Practices for Naming API Endpoints.” 

Tip # 3: Respect Your Own Process

An experienced API designer can push through same-day delivery: “You can whisk through the discovery, design, development, and deployment processes, but you’ll end up with a suboptimal product. Instead, stick to the approach that works, and accept that creating or updating an API will take a little longer than others might like.” To build a strong API, respecting the need for thoughtful progress through the process is essential. 

Tip # 4: Build the Complete Ecosystem

An API is just the jumping-off point. It’s just as important to create quality SDKs, a reliable sandbox, and a support staff ready to handle the bugs. These elements elevate the the quality of the core API products. 

Tip # 5: Stick to Rigorous Standards

An API governance system of internal organizational or communication structures will keep the work a consistent quality. Rahul is guided by Conway’s Law in this thinking.

Final Takeaway

The best APIs are built with design ground rules rooted in common sense. A uniting governance based on rigorous standards, knowing your target developers well, thoughtful nomenclature, and giving the support assets as much attention as the main product.

Go to Source
Author: <a href="https://www.programmableweb.com/user/%5Buid%5D">Katherine-Harrison-Adcock</a>

Categories
Hackster.io

Nordic Thingy:91 // MCU Monday

Let’s unbox the Nordic Thingy:91, a hybrid cellular IoT device combining LTE-M Narrowband IoT (via the nRF9160 SiP) with short-range BLE, ZigBee, and other protocols (using the nRF52840 SoC). Pre-programmed for asset tracking, this module has a full complement of sensors – a GPS receiver, accelerometers for impact and orientation, light sensing, air quality, and more – plus user interfaces such as a programmable button, buzzer, and LEDs.

In our next video, we’ll connect the Thingy:91 to nRF Connect for Cloud, an online dashboard where you can manage devices and sensor data. Stay tuned!

// https://www.nordicsemi.com/Software-and-tools/Prototyping-platforms/Nordic-Thingy-91
// https://www.nordicsemi.com/Products/Low-power-cellular-IoT/nRF9160
// https://nrfcloud.com
// More info: https://www.youtube.com/playlist?list=PLx_tBuQ_KSqGtprnjJeiscwhPgYM0CkIS

Categories
Hackster.io

nRF5340 PDK Unboxing!

Today, we’re unboxing (dis-enveloping?) the new nRF5340 Preview Development Kit from Nordic Semiconductor ASA! A low-power, multi-protocol wireless controller with dual Arm Cortex-M33 cores and a heap of security features, this chip is ideal for lighting systems, wearables, and more.

// https://www.hackster.io/news/nordic-semiconductor-announces-the-new-nrf5340-micro-controller-9014f5841168
// https://www.nordicsemi.com/Software-and-tools/Development-Kits/nRF5340-PDK
// https://www.nordicsemi.com/Software-and-tools/Software/nRF-Connect-SDK/GetStarted
// https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/introduction.html

Categories
Hackster.io

Nordic Releases Thingy:91 Multi-Sensor IoT Prototyping SiP

Back in 2017, Nordic Semiconductor released their Thingy:52 IoT prototyping platform designed around the nRF52832 Bluetooth 5 WiSoC, which was aimed at quickly building prototypes quickly without the need for excess hardware or even the need to write firmware code. The company has recently unveiled a new IoT development package aimed at cellular applications with the Thingy:91 multi-sensor prototyping platform.

The Nordic Thingy:91 is designed around the nRF9160 SiP, and is suited for cellular IoT applications that use LTE-M, NB-IoT, and GPS. (📷: Nordic)

Thingy:91 is based on the nRF9160 SiP, with LTE-M, NB-IoT, and GPS connectivity, which Nordic says is ideal for creating proof-of-concept (PoC) projects, demos, and initial prototypes in the cIoT development phase. In fact, it comes preloaded with an asset-tracking application to get started with those applications. Under the hood, the Thingy:91 features an Arm Cortex-M33 core, with 700–960 MHz + 1710–2200 MHz LTE band support, CE/FCC certifications, an nRF52840 board controller, and LTE-M/NB-IoT/GPS, Bluetooth LE, and NFC antennas.

The platform also offers a Nano/4FF SIM card slot, user-programmable button, RGB LEDs, buzzer, four N-MOS transistors (for external DC motors or LEDs), and rechargeable Li-Po battery with 1,440mAh capacity. There’s a slew of sensors too — including temperature, humidity, air quality, and air pressure, as well as a color and light sensor, low-power accelerometer and high-g accelerometer. It even packs an nRF52840 multi-protocol SoC that supports multiple short-range wireless technologies, such as Zigbee, Bluetooth 5.0, Thread, and ANT.

Nordic’s Thingy:91 comes in a rubberized case with a USB port to charge the internal Li-Po battery, and is programmed using the company’s nRF Connect SDK with integrated Zephyr RTOS. The platform is available from several vendors with pricing starting at $119, and more information can be found on the Thingy:91 at Nordic’s product page linked above.

Go to Source
Author: Cabe Atwell