The first Kio Kit customers

Last year when we launched our ruggedised Kio Kit, what followed was a ton of interested buyers. It gave us both huge hope and nerves that our product was going to schools. Prior to launch, we had piloted the Kio Kit in some schools and that gave us a lot of user experience feedback. Now however, it was time to find buyers and ship them off to new users.  

Our first customers unexpectedly turned out to be students. International school of Kenya’s students huddled together and made the first purchase as a donation to a primary school in Nanyuki – Irura Primary School through their inter-cultural program. Irura Primary School is about 20Km from Nanyuki town and about 6Km from Ol Pejeta’s Rongai Gate. The students come from the nearby community, beyond being surrounded by an expansive wildlife conservancy, they are nested away in rural like settings.

Since our first Kio Kit deployment, we have learnt and improved many times over. From teacher training to content preparation, over time this experience gave us many learning lessons that we have certainly benefited from. Our first customers and school feel special to us, in a way we have only learnt what that means almost 1 year later.

Improvements to the Kio Kit.

Irura Primary being the first to deploy the Kio Kit has been a long process of learnt improvements. We began to learn key things such as how to better manage the content, to supporting hardware issues. There were hurdles that since then over 9 months has been significant to making improvements that are now applied on the Kio Kit.

Supporting Teachers

When we launched the Kio Kit we had some ideas of what impact it would have on both the students and the teachers, however our calculation was theoretical. We imagined it. It has been revolutionary to see how teachers benefit from using the Kio Kit. They have taught us how to make improvements, not just by making it easier for them to find content for their classes but also aiding them with lesson plans and giving them additional teaching tools to support them. Teachers love using the Kio Kit in class because it’s a helpful teaching tool. The students are able to focus better in class, they pay attention to what they are learning with ease and they don’t get distracted easily during their lesson.

Students

Schools like Irura that are away from cities and in rural towns are usually lacking in facilities and learning materials. Most students don’t have textbooks or enough of them and even finding writing materials is difficult. Without some form of technology, learning for these children would be difficult. The Kio Kit provides a great alternative to learning and beyond that gives the child a grasp of what technology looks like in this century. ISK also provides content which they share with Irura students. This content, created by ISK students helps their peers not just watch, but also understand what their peers have made in this cultural exchange.

Kids by Kids

Learning through peers is a great way to gain greater understanding of educational material. ISK students took this in an interesting approach. Their cultural exchange program got them interested in learning about the folk tales and traditional stores the students in Irura had learnt through generations. These stories were then translated, drawings and narration added to make small animations.  Today the content is available on the Kio Kit.

Many Thanks

Our trips to Irura Primary were coordinated with the help of Rift Valley Adventures. They played a big role in setting up a computer lab at Irura as well as hosting us many times when we would take the trip to Nanyuki. Endless thanks to Dipesh Pabari who didn’t tire in getting our team together with both ISK and Irura Primary.

A year on and full of hard work, looking back we learn a lot from our first deployment. These lessons and many more fuel incessant changes to move our product in the right direction.

This morning finds us on the road north of Nairobi, heading to Samburu country in northern Kenya. [Actually, it finds us delayed by 2 hours as we troubleshoot a bit of the new education software, but that’s besides the point!]

Each year we do an expedition, last year we did a trip to Uganda testing around education. The year before that we went up to the shores of Lake Turkana. Here’s a video from our trip last year to South Africa overland:

Kenya to South Africa / Nairobi to Johannesburg from BRCK on Vimeo.

Samburu Schools

This year we’re going up to Samburu county to do two installations of our BRCK Education school system called the Kio Kit. This kit comes with 40 seven-inch tablets that are all wirelessly charged and the BRCK device acts as the brains of the network, loading content supplied by a number of different partners. All the info on the Kio Kit is in this video below.

We Introduce the Kio Kit from BRCK on Vimeo.

The trip north takes us to a school near Archer’s Post, and then a couple days later to one near Korr. Both of them are well off the road, but have been electrified by the Kenya government’s school electrification program. So, while we’re going with some extra solar kits, we’re expecting to be able to use the school’s power system.

On this trip is Mark (UX), Jeff (Design), Nivi (Education), Janet (Ops), Rufus (Customer Service) as well as Philip, myself, Juliana and Peter. It’s a full roster and we’re looking forward to having an adventurous road trip.

We’ll be posting on this trip for the next few days, so you can follow along here on our blog, on our Twitter account @BRCKnet and on our Instagram account @BRCKnet.

With all the hubbub about the team’s epic three week dash to South Africa and back, some may have forgotten that only a month and a half ago, the other half of the team were cruising Lake Victoria and the Nile in Uganda. The video edit is done, though, so we’re bringing it back!

We started off with a plan to work with Johnny Long of Hackers for Charity to connect schools around Jinja to the internet and learn from local educators how we can build technology that meets their needs:

http://brck.com/2014/11/brck-expedition-2014-exploring-edtech-on-the-water/#.VJP-mACU

We wound up visiting the Living Hope Secondary School on Lingira Island in Lake Victoria:

http://brck.com/2014/11/brcked-expedition-connecting-lingira-secondary-school/#.VJP–ACU

http://brck.com/2014/11/brcked-expedition-part-two/#.VJP-8ACU

On the boat ride back, we broke out our OpenROV underwater exploration robot:

http://brck.com/2014/11/going-deep-with-openrov/#.VJP_JACU

Finally, we took a raft trip down the White Nile to play with antennas and sensors, to see how the Internet of Things could help conservation efforts in threatened ecosystems:

http://brck.com/2014/11/how-the-internet-of-things-can-help-save-our-rivers/#.VJP_TACU

You can see all that and more (read: zany BRCK team adventures) in the video above. It’s been a heck of a year for us here in Nairobi, and we can’t wait to see what 2015 brings! (Did someone say they need a weather station on Mt. Kenya…?)

It’s funny what causes one to get excited. For some it is the smell of something new. For others the satisfaction of helping someone out. For me, it is the magic of seeing something that we designed come together into a product that is more than the sum of its parts.

In the very early days of BRCK we envisioned this amazing expansion ability. We added USB lines and power connectors. We had some vague ideas of what this might be used for but I don’t think that we could have imagined the device that I am now holding in my hands. This is, simply put, the coolest piece of tech kit that I have yet to experience.

Ok, I hear you saying, but it is your company’s tech so obviously you think it is cool. Sure, I am biased but then it isn’t really the actual device that has me so excited. What really has me excited is the potential of what this device could mean for people across Africa – particularly school children.

Simply put, the BRCK+Pi takes all of the ruggedness, power resilience, and connectivity flexibility of the BRCK and adds incredible application processing capabilities. A BRCK on its own is capable off serving up static content but a BRCK+Pi is capable of rich interactions and locally hosted applications. In our view, this creates the potential for a new computing UX paradigm at the edge of the network. A paradigm where “the” cloud might not be “The” Cloud. Where communities can access the content that is relevant to them without being perpetually connected to the rest of the internet. An opportunity to change the way we think about educating the 400 Million plus school children on the African continent.

This wide reaching potential is what makes the BRCK+Pi such an amazing piece off technology – regardless of who developed it.

I first wanted to write about this new product we are developing when Reg and I actually plugged the two devices together and served up our first web application. It was a cool moment and I really wanted to share it with the world. That was six weeks ago and Reg was frantically preparing to head to Mozfest for the official announcement of BRCK+Pi. As so often happens in a small company with too few resources, I started the post but never finished it.

Fast forward to today, Nov 24, and the BRCK team is sitting at a camp next to the Tarangine park in Tanzania on the first day of our epic overland expedition to South Africa. As we sit around the fire warming sore muscles from a long day of riding, Erik and I are uploading and sharing our images on the BRCK+Pi media server that Kurt built for us. Since we are gluttons for eating our own dog food, we wanted to put this amazingly cool device to proper use as we work our way across 9,000km of southern Africa.

As if sitting in camp and having a fully functioning media server running from an integrated BRCK stack wasn’t enough, we just so happen to be in an area with limited backhaul over the cellular lines. We are fortunate enough to have one of the iSavi devices from Inmarsat to provide satellite backhaul from anywhere on the planet.

So as I am typing this, as we sit by the fading fire under the African stars, we have a BRCK getting connectivity through an iSavi connected to a Pi that is providing our media storage as Erik and I are seamlessly exchanging and uploading media so that we can share our latest BRCK story with the world.

While our current use case may not save the planet, there is no doubt that the lessons we are learning this evening will have a lasting impact on our ability to redefine the ideas of computing at the edge of the network and in emerging markets – especially Africa.

It’s that time of year in Kenya again – the “short rains” are coming, there’s a slight chill in the air, and every now and then, the sky opens up for a brief deluge of water. It’s hard to avoid getting wet during the rainy season here, something we’ve designed the BRCK to handle (in small doses, at least).

It just so happens that one of our key partners, Hackers for Charity – who help schools and nonprofits solve technology related problems so they can get on with their jobs – has some interesting problems they are trying to solve in their work with schools around Jinja, Uganda, at the source of the White Nile and on the shores of the largest body of water in Africa, Lake Victoria. Time for a water-bound expedition, methinks.

Going into the wild to test our products in some of the most remote and challenging environments we can find is a core principle behind how we design in Africa, for Africa; to eat our own dog food, so to speak. Last year we took a trip to the barren shores of Lake Turkana in northern Kenya to live stream one of the best views in the world of a hybrid solar eclipse. Despite having that view blocked by a massive dust storm, the BRCK performed admirably, and we learned a lot about how to design for reliability in extreme weather. You can watch the video here:

This year, we’re taking a slightly different tack. When we started making the BRCK, we found some of the greatest need for affordable, reliable connectivity is in schools. We’ve been pushing hard for solutions in the edtech scene ever since, working with partners such as eLimu, Mozilla, and Sugata Mitra’s “School in the Cloud” TED prize wish to develop projects around innovative caching solutions to cut down the costs for data, a Raspberry Pi MRTR to turn your BRCK into a remote server, and testing connectivity solutions in schools from India to Ghana.

When Johnny Long, the founder of Hackers for Charity, first contacted BRCK back in June, he showed us his own attempts to build a rugged and reliable remote connectivity device. It looked remarkably like some early BRCK prototypes. It was clear we were trying to solve the same problems, and that by working together we could make a dent in the challenges facing students in rural Uganda. We set Johnny up with a BRCK and gave him free reign to hack it however he needed to build the solutions that worked for the schools he and Hackers for Charity supports.

At last, we have the chance to work with him directly. On Sunday, six of us will load up the Land Rover and make the 12-hour journey from Nairobi to Jinja. Johnny has graciously offered to host us at the bed and breakfast he and his wife run while we set about training up the Hackers for Charity staff on the technical aspects of the BRCK, testing antennas and signal amplifiers, and ultimately working to get several local schools online.

One of these schools is on an island in Lake Victoria, an hour and a half journey from Jinja by boat. Seeing an opportunity to kill two birds with one stone, we decided to bring an OpenROV with us. We’re hoping we can work out a way to control the ROV through the Ethernet port on a BRCK, meaning we could “wirelessly” pilot the ROV through the waters of Lake Victoria. Since Ushahidi, our parent company, partnered with OpenROV to create OpenExplorer.com, a platform for sharing the fruits of grassroots exploration with the world, you’ll be able to follow the progress of the entire expedition at:

https://openexplorer.com/expedition/brckexpedition2014

As if this wasn’t enough, Jinja also happens to be at the headwaters of the White Nile, with some of the best high-volume whitewater in the world. A BRCK expedition can’t be all bed and breakfasts, so we looked up Pete Meredith, one of the leading explorers of the Nile (he’s ran it from the furthest source in Rwanda all the way to the Mediterranean), and Nalubale Rafting to help us spend a couple days exploring the river.

In addition to the edtech sphere, some of the primary use cases that are emerging for BRCK’s technology are around conservation. We’ve been talking to people who are monitoring the effects of hippo feces and wildebeest carcasses on water quality in the Maasai Mara and streaming live data on animal sightings and pH levels (and much more) in the Okavango Delta in Botswana. You can read all about the Mara Project and Into the Okavango here and here:

http://mara.yale.edu ; http://mamase.unesco-ihe.org

http://intotheokavango.org

Both of these projects have very kindly shared info about their open-source sensor package designs with us. We’ve put together our own package to test pH and water temperature, and will attempt to stream data from the river as we go. This will be a fantastic learning experience as we further develop IoT use cases for the BRCK, and we hope will prove a valuable source of insights for how we can better enable our conservation partners to inform the wider public about the amazing work they’re doing, and the importance of these fragile ecosystems.

So, with a very full docket, our soldering irons packed, and our heads and hearts full of excitement, the BRCK team is once again setting out into the wild blue yonder. Get ready to follow along – BRCK Expedition 2014 begins tomorrow!

So, you want to hack your BRCK, eh? Good for you! There are all sorts of goodies inside that you can use to do everything from monitor remote sensors to boil water (with a couple infinite loops thrown in your code, of course).

If you want to take your BRCK apart, just be aware of two things:

1. You WILL void your warranty. We strongly encourage innovative uses of our hardware, but we can’t be blamed for what happens. This is fun stuff, but if you break your BRCK, we won’t replace it.
2. Be very careful removing the modem. The flex cable underneath it can break if you work too quickly.

Happy hacking!

BRCK How To: Tear Down from BRCK on Vimeo.

Welcome to a new series of videos called BRCK: How To’s!

We’re kicking things off with a step-by-step walkthrough of the first thing you’ll want to do when you get your BRCK: register it. Learn everything from what the lights mean to how to handle some commonly encountered issues. Enjoy, and see below for a description of the registration process!

BRCK How To: Registration from BRCK on Vimeo.

Registration process:

To setup your BRCK for the first time, plug it in and turn it on. The lights will tell you what it is doing.

The center light tells you your power status:

• Red < 10%.
• Yellow < 40%.
• Green < 95%.
• Blue < 100%.
• Pulsing indicates that your BRCK is charging.

The outer lights indicate your connection status:

• Spinning means the BRCK is searching for a connection.
• Solid outer lights mean your BRCK has established a connection. The outer ring will pulse at a rate that indicates your connection speed.
• Orange is for the BRCK’s internal startup process.
• Purple is for Ethernet connections.
• Green is for WiFi bridging.
• Blue is for 3G.

Visit my.brck.com/help for a helpful guide to the color scheme.

To register your BRCK, it needs to be connected to the Internet. After you turn it on, do one of the following:

• Plug in an Ethernet cable from another modem or router.
• Insert a data enabled SIM card.
• Or use the local dashboard to configure a WiFi bridge (more on this below).

Go to your WiFi list and look for your BRCK. It will appear as “BRCK_somelongstringofnumbers”.

Connect to it, open your browser and go to my.brck.com.

If you have an Ethernet or SIM connection, you will be taken to the registration page and can skip the next step.

If you do NOT have an Ethernet or SIM connection, you will be redirected to the local dashboard where you can configure a WiFi bridge:

• Click “View” under WiFi.
• Select your network.
• Enter your password.
• Click join.
• Wait patiently while your BRCK configures these changes (this can take several minutes).

Once you are directed to the registration page, click “Sign up”.

• Enter your name, email, and choose a password.
• Click “Create account”.
• Once your BRCK has finished applying these changes, click “Go to your dashboard”.

You will be taken to the cloud dashboard for your BRCK, where you can see statistics regarding your power status, data usage, and devices connected to your BRCK.

Click on “Preferences” in the left pane to change your connection configuration.

• To change the name of the WiFi network your BRCK broadcasts, click in the box under “WiFi Name”.
• Enter a new name, set a password, and click “Save”.
• You may see an error message at this point. This happens because once you’ve changed the name of your BRCK’s WiFi network, your computer will lose connection to it and the cloud dashboard.

To reconnect to your BRCK’s new WiFi network:

• Open your WiFi list.
• Your BRCK’s new WiFi name should appear shortly.
• Connect to it, et voila!

Congratulations, your BRCK is now registered! You can access the Internet, the cloud dashboard, and configure your BRCK from anywhere in the world.

Building BRCK – Assembly from BRCK on Vimeo.

[Some shots from the factory, building BRCK, this week.]

I know that we weren’t naïve in the early days of BRCK thinking that it would be easy to build an amazing hardware device in Kenya. We couldn’t have been. We aren’t rookies. This isn’t our first rodeo – as the expression goes – and yet we still find ourselves months behind on getting our product shipped. Did we miss something obvious in our planning? Were we unrealistic about our capabilities and capacities? Did we simply have some incredible misfortune?

Honestly, the answer to all of these – at least on some level – is yes.

Sure, Reg and I have experience in bringing hardware products to market. We know the pitfalls of having injection-molded plastics made in China not looking correct. We’ve made small mistakes on board layouts that required last minute hand fixes and reworks. We’ve had suppliers completely drop the ball in meeting their delivery commitments. These things are absolutely normal and expected in designing hardware products – particularly if your entire company sits in the same room as the soldering irons and oscilloscopes.

On the software side, Emmanuel, Wesley, Erik, and I have all brought software systems and products to market. We have sat in the meetings were we suddenly realized that a critical feature/function had been completely overlooked. Participated in the user testing sessions where the look of bewilderment on the face of the tester causes your heart to sink into your stomach. Pushed ourselves through “highly productive” 3 am coding sessions that take hours the next morning to unravel in the clearer light of day. This is the reality of startup software engineering in the age of Android and Flappy Birds – actually I think it has always been this way.

We know these realities. They aren’t foreign or unexpected to us. And yet with every delay or misfortunate turn of events we still all stare at each other in shock and disbelief. We expect things to be different at BRCK. We see ourselves as a rugged and tenacious group of creatures that have our skin thickened by the hot African sun and our eyes steeled to navigating the rocky road ahead. It’s who we are. When we adventured out on BRCK Expedition Turkana we should have seen that this was a harbinger of things to come: trucks breaking down, satellite receivers mysteriously running out of credit, routes getting flooded, and the unlimited supply of things-not-going-as-planned. Sure we got frustrated. At each other. At the circumstances. It’s a natural human reaction. But we never gave up. We didn’t even entertain it in conversation. We all dug deep into the beautiful resource called human spirit and plowed ahead until we reached our goal. Sure we’ll do some things differently on the next expedition, we are fools to not learn from our experiences, but we know that the only thing that really matters in setting off is our collective resolve to persevere and push on towards the mark.

Which brings me back to BRCK. Earlier this week we finally received our delayed set of production plastics from China. They were awful. They looked nothing like the first articles that had previously been sent through or the amazing cast cases that were molded from 3D prints. As we sat and stared at the disfigured hunks of plastic that were meant to hold the product of months of hard work our hearts – once again – sank and we stared at each other in disbelief. Although we briefly entertained proceeding with production using the “ugly” cases, we know that we are flag bearers for engineering and designing products the right way in Africa. While we live in a culture where the standard of craftsmanship is often “good enough” we must be an example for something much higher.

So we are sadly forced to delay our production one more time and ask for patience. Patience from our customers who are eager to get their hands on a BRCK. Patience from our team as we continue the sprint to get BRCK to market. Patience from our backers who have shown so much faith in our vision and the potential for BRCK to be a game changer in the market. It’s a big ask on our part and we don’t make it lightly. We won’t sit back during this time and simply wait. There are many things that we know we can do better on the software and usability side of BRCK. We will continue pushing ahead on making the user experience more intuitive and useful. We will take our handful of ugly BRCKs and put them to the test in as many challenging situations as we can find. We will do everything within our abilities to use this misfortune as an opportunity for making BRCKs better. As painful as it is for us to be in this situation today, I know that at the end of this journey we will look back and be grateful for the additional opportunity to ensure that BRCK really lives up to its full potential as a world-class hardware device from Kenya.

We’re working with our case manufacturer to get a new timeline for delivery, which we’re expecting to be no more than a few weeks.

Since we last updated you a month ago, a lot of great things have been happening.

Reg and Erik are on their way to Austin, speaking at SXSW on Friday. If you’re in town, do come by and talk to us. We’ll have some BRCKs with us and will show you how it’s going. You can also ask any questions and geek out with us on what you can do from the software and hardware sides to extend the BRCK core functionality.

Though Austin is always a fun place to be for SXSW, this isn’t the only reason we’re there. While the BRCK is designed and engineered in Kenya, the final assembly and manufacturing is done in the US – in Austin, TX. We’ve started our production orders, production boards are being flashed, and we’re doing regulatory testing now as well, trying to get that all accomplished quickly so we can get your BRCKs to you as fast as possible.

Some other goodies:

The BRCK Eclipse Expedition A couple months ago you might remember that the BRCK team was chasing a rare hybrid eclipse in Northern Kenya, to the shores of Lake Turkana. If you missed out on following our adventure, you can read about it on Erik’s Blog. Here’s the video of that trip:

BRCK Eclipse Expedition to Lake Turkana from BRCK on Vimeo.

Boxes and Dashboard Sneak Peek

Jeff Maina joined the team in February and we’re excited to have someone of his design skills on the team. Here’s a sneak peek of the box and the dashboard.

Jeff holding the BRCK packaging (note: the final will be cardboard colored, not white).

Both Jeff and Emmanuel have been crunching out a bunch of pixels and code, so that everything from the initial setup process to the dashboard work. It’s all completely responsive design, so that you can access it via your browser on a phone, tablet or computer.

The Sandstorm (@SandstormKenya) team in Kenya is making the special pouches for the BRCK backers who came in at over $300. The original design was cool, but they just came back to us this week with an even more amazing and rugged case made of canvas, leather and brass. It feels like we moved from a Landrover to a Range Rover with it!

But, when does the BRCK ship!?

This is the date we’ve been hunting as much as you. It’s been a longer road than we though, due mostly to component manufacturing issues and having to redesign things at the last minute. While we could have pushed out a basic BRCK earlier, it would not have been something that you (nor we) would have been happy with. Assuming all of the final issues lined up around components, assembly and regulatory issues, the BRCK should ship in April. We’re bending all of our time, energy, sweat and tears towards making that happen. Thank you for your patience!

Erik Hersman, for the BRCK team

The BRCK is designed and developed here in Nairobi, Kenya. As you might expect, this is a very different experience than doing it in China, US or EU. While creating physical products is always hard. Doing it in Africa is harder. This is due to the difficulties around rapid prototyping, shipping costs and accessibility of components. However, it’s also the best way to understand the real problems and challenges that the BRCK is here to solve.

Reg Orton, BRCK CTO, is on this short video explaining some of what this means:

BRCK: Designed in Kenya from BRCK on Vimeo.

Some key thoughts on this from our end:

• We are not an off the shelf solution and rebranding
• We are pushing the limits of what is possible to do without
• Retail price point dictates smart design and challenging design
• We want our engineers close to the problem to really understand the requirements. This makes things harder than if we were designing in China
• We are developing a far better product by doing custom design
• Our volumes are lower in this market segment than if we were designing an ordinary router device.
• We are developing a company here, not a fly by night product. We want our v2 and v3 products to be heads above everyone else.
• Doing this allows us to rethink a lot of the assumptions that existing products use.