The Lewa Marathon: My Experience

Lewa Marathon Team Photo

Camping, outdoor fun, and keeping fit are part of an undocumented culture within BRCK. You see, more than half our team is always very excited when there is an outdoor activity. The Lewa Marathon is a significant activity on our calendar and BRCK has taken part for the past four years. This experience is purely about spending time in the wild. From running the 21km marathon to spectating, it’s a wonderful three-day period. We got to bond with workmates, kids, partners, and friends, all with the goal of conserving our wildlife.

I have been to Lewa twice, the first time in 2018 as a spectator, cheering on my teammates. Little did I know that it would be me the next year. In 2019, I went as a runner, determined to race in the marathon. Yes, you read that right; I did 21km, and I survived!

The trip to Lewa involves several stops, but as Izaak Walton once said, “Good company in a journey makes the way seem shorter.” After a long drive, our team gathers at the campsite to set up camp. When we arrive, some members prefer going for game drives to enjoy seeing the beautiful wildlife. The Big 5 tend to come out in the evening so we had to take advantage. We saw a lion, elephants, buffaloes, and rhinos, among others.  We were lucky to have our colleague Cyrus capture the amazing scenes and moments. The first night is usually relaxed and quiet compared to Saturday evening. This is because the runners need a good rest in readiness for the morning task. We usually have a bonfire set up as it gets dark. 

Lewa game drive   

Doing 21km is not an easy task and takes a lot of preparation. We started practicing in March, with monthly runs in Karura as a team. We encouraged each other on how to go the extra mile each time we ran. The first time we did a 10km run was my wake up call. I ended up walking for 9kms… Things had to change, so I started exercising three times a week. I would also run 10kms every two weeks to keep fit. It got easier with time and by June I was somewhat ready for the task that lay ahead.

My main goal was to finish, because those who had done it before told scary stories about the experience. We were up early on the chilly Saturday morning. I was super excited and nervous at the same time. We got to the starting point as a team and, of course, we had to capture the moment, which in the true sense turned into a mini photoshoot. Those who know me know my love for pictures runs deep. The warm-up dance at the starting line was so exciting and I had to keep reminding myself that I could do it.

 

Marathon starting line

Our motto at BRCK is “You Can Do Hard Things.” This was an arduous task, but I was determined to crush this milestone. I love project management, so I always end up dividing my tasks into smaller bits. The gun to start the race went off and I remember having a meeting with myself to affirm that I was competing with no one. I was running for a cause and all I had to do was to get a medal at the finish line. I didn’t start in a rush, I kept my pace for the first 12km and it was amazing. The hills from 14km were not easy, but I was determined to finish, so I kept going.

The organizers took great care of the runners. We had water points every 2km that also had energy drinks, fruits, and a cheering squad and, to be honest, this made the pain a little more bearable. I expected our team to be at every water point, but I was being too ambitious. But when I got to 10km, there they were. When I saw them, I think my energy levels tripled. 

Marathon

My legs decided to take a break when we got to 18km. 3km at Lewa is like 10km in Karura. I struggled to get to the finish line, it was the longest stretch I’ve ever run. I was tired and drained. The water and the fruits helped, but could only do so much. I did all I could to keep encouraging myself in the last phase, and I walked and jogged concurrently. I kept reminding myself that it would get better and before I knew it… I was at the FINISH LINE, having finished on my two feet and without dying in the process. The most exciting thing at the finish line is that you get a medal, a Safaricom gift hamper, a deep tissue massage and the pride of knowing you finished the race.  

When it was all over, I felt extremely accomplished. I set a goal and I accomplished it, finishing the race in under three hours. Although I would have been happy to just finish, I also had a secondary motivation during the race… to finish before Paul Obwaka. You see, Paul is one of my colleagues and he made fun of me, saying how he could finish before me even if he ran in reverse. But as the saying goes, “Don’t count your chickens before they hatch.” I ended up finishing two minutes before him and best believe I am enjoying the feeling of this moment.    

If someone had told me in January 2019 that I would train and run a half marathon, I would have thought they were crazy. But now, a few weeks later, I know I am addicted to that feeling of accomplishment. 

The hardest part is signing up, but BRCK made that process easy for us. So at BRCK, the thing that can keep you from succeeding is if you don’t show up and put in the hard work. Running and competing in the marathon offers so many benefits, so I will definitely do it again next year. It’s a habit I have added to my list. And if I can run a half-marathon, anyone can.

Inspiring the Next Generation of Leaders

From the 15th to 17th of January 2019, four students from the ALX Launchpad (a leadership accelerator program) joined BRCK to get a feel of how the company operates.

ALX students with BRCK employees
Excited at the end of a fruitful week of interacting and learning

Each of the students shadowed an employee of BRCK based on their career preferences and they had the following to say during their short stint at the company:

Leila Ali

I have always been fascinated with data. I love numbers. For the three days that I shadowed at BRCK, I got an opportunity to meet really awesome people who not only inspired me but also were willing to share their knowledge in technology. I was placed in the operations department under Brian Birir, the operations data & network supervisor, and he taught me a lot. From data extraction, transformation, and visualization to programming, BRCK is a really cool organization and hopefully after I finish my studies in software development and programming I can come back to work for them.

Samantha Mwenda

I had always admired BRCK from afar, so this week was a true opportunity for me to see the inner workings and how everyone came together to achieve the company’s goal, especially from the design angle. I was lucky enough to be placed with the design team and I was extremely excited! I learned a lot from the brilliant minds at the table and would hope to interact with them more.

Each person that I spoke to was willing to fill me in on what they were doing and how they were going about it, which I really appreciated. From UX to UI and front-end, everyone in the team played their part in making the BRCK brand what it is today. I also really appreciate how everyone in the company made us feel at home and warm. The culture was very tangible unlike other companies I’ve interacted with. Thank you for making that week what it was.

Stacy 1.0 & Stacy 2.0

Our first day at BRCK was all levels of awkward at first, now that I have a superpower of getting comfortable even with awkward silence, and Stacy 1.0 is a typical people person. I took the first hour to just settle in and breathe, not knowing what to expect from the world of technology (that we thought didn’t match our preferences). And that beautiful motto “You can do hard things” made us feel at home instantly because it is the same as our ALX motto.

Before it could all escalate, we had a sit down with the Project Manager. Literally two minutes into the conversation, we learnt so much about what her job entails. We love our project management class so seeing actual Gantt charts and weekly reports made us light up. This experience gave us the confidence to explore what other people in the commercialization team do. We had eye opening conversations about the world of digital marketing and got tips about how to leverage our degrees in the field of marketing and got to understand the vision behind BRCK.

We loved the seamless connection of the different departments to create mind-blowing final products. Shadowing BRCK was a blast and a definite turning point for us. We have been motivated to work in a startup environment and in many ways confident to pursue a career in marketing and communications (or as y’all call it … commercialization). So thank you a lot for this opportunity. And as we continue to ‘Do Hard Things‘, we only hope and pray our paths cross again.

 

Reflecting on 5 Years of BRCK

It was 5 years ago that we created BRCK as a company, and I’ve had the great joy of being on a journey with some fantastic people, including the three here with me in this picture (Reg Orton, Emmanuel Kala, and Philip Walton).

We had an idea of what we were getting into back in October 2013, but none of us were sure where it would actually take us. All we knew then was that the barriers to creating hardware had dropped enough for us to get into it, that there was a problem in the internet connectivity space in Africa (and other frontier markets), and that we had the right mixture of skills, naiveté, and optimism to figure it out. Over the next 12 months we grew to a team of 10 that had this the desire to meet a big challenge and believed we could do hard things. As I write this, 8 of those 10 are still at BRCK.

In the intervening years we’ve built three full products and taken them to market (BRCK v1, Kio Kit, SupaBRCK), and a fourth (PicoBRCK) that is still in R&D. That alone is quite an accomplishment. I hadn’t known back in 2011, when the idea for creating a device was first hatched, just what the life cycle of building a hardware+software product would be. I do remember having a conversation with an old friend, Robert Fabricant, that I thought we should be done with the first one in about a year. He laughed and said it would be at least 2-3 years. He was mostly right.

[foogallery id=”4816″]

I’ve since learned that it takes approximately 18 months for a product to go through the concept, design, testing, productization, and first samples stages. Then it typically takes us another nine months for iterations and small fixes on hardware to happen, while that same time is spent concurrently hardening up the software side of things. For example, our most recent SupaBRCK took approximately almost two years from conception to product, and then another six months of continued fixes/changes to the low-level software and the hardware, before it worked well consistently.

Asking the Right Question

You would often hear us saying, “Why do we use hardware designed for London or New York, when we live in Nairobi or New Delhi?” as a way to frame the problem we thought we were solving. It was only in late December 2014, after we had shipped the BRCK v1 to 50+ countries, that we realized we were only partially on the right track.

It turns out the problem isn’t in making the best hardware for connectivity in difficult environments. Sure, that’s part of the equation – making sure that you have the right tools for people to connect to the internet. But the bigger question involves people. Who is connecting to the internet and who isn’t? If, after many years of building BRCK, we had built the best, most rugged and reliable solution for internet connectivity, that would be something we could pat each other on our backs for. However, if the problem instead was “How do we get the rest of Africa online?”, and we were able to solve that problem, then that was a legacy we’d be proud to tell our children about one day.

Sitting in our tiny office around Christmas 2014, we started thinking hard about this bigger issue and began doing deeper research into the problems of this loosely defined “connectivity” space. We started doing some user experience research, man on the street interviews, to figure out what the pain points were for people in Kenya.

Connectivity can generally be broken into two buckets:
First, accessibility – can I connect my device to a nearby signal?
Second, affordability – can I afford that connection?

The results were quite telling, it was definitely about affordability.

For everyone who’s not deep in African tech, let me lay out some interesting numbers for you. Accessibility in most of the emerging markets has been moving rapidly since the mid-2000s when we started to get the undersea cables coming into the continent. These cables then went inland and started a rapid increase in available internet connections and wholesale internet costs decreased rapidly. Since 2008, we’ve had more than one million kilometers of cable dug across the continent, and we have over 240,000 cell phone towers. Concurrently, the mobile device prices continued to drop globally, and by 2016 we started to have more smartphones imported into Africa than non-smartphones.

Reaching deeper into the market research, we started to study this affordability problem.

A4AI found that the average price of 1GB prepaid mobile broadband, when expressed as a % of average per capita Gross National Income (GNI), varied between 0.84% in North America and 17.49% in Africa.”

It turns out that in almost every country in Africa, there is a consistent ratio among all the smartphone owners in a country: 20% could afford to pay for the internet regularly, and an incredible 80% couldn’t.

Interestingly, when we looked at who else was working in this connectivity space, almost everyone was focused on accessibility, not affordability. Those who were focused on affordability thought that just making the price cheaper was enough. What we’ve seen is that if you just make “less expensive” subscription WiFi (as most do), then you’ll capture another 10% of the market. And while that can make a profitable enterprise, it still leaves 70% of the market unaddressed.

This last blue ocean of internet users in Africa, as well as Asia and Latin America, is still largely ignored. Those who do have the resources to go after it tend to try with iterative approaches in both business models around affordability, and only marginal creativeness in solving for technology accessibility.

Moja Means ONE

It’s taken us 5 years, going through multiple iterations of new tech, building new hardware, and creating new software stacks that go from the firmware up to the cloud. We’ve been mostly quiet for the past year as we put our heads down and tried to take a new platform to market. Where are we now?

“Moja” means “one” in Swahili, and it was the brand name that we chose to call the software platform that we would build on top of the BRCK hardware. While Moja means one, “pamoja” means “together” or “oneness”, and that was the root we were looking for. To us, Moja is the internet for everyone.

We started by trying to make it work on the BRCK v1, but that was a bit like trying to make a sedan do a job built for a lorry (truck) – it wasn’t powerful enough. The SupaBRCK was envisioned as the hardware we could leverage that would allow us to not just have enough of a powerful and enterprise-level router, but a tool that was actually a highly ruggedized micro-data center. With this, we could host content on each device, as well as get people connected to the internet. Another way to think about the accessibility side of what we do is that we have a new model for how a distributed CDN works on a nation-scale, moving away from the centralized model that the rest of the world uses. In environments like Kenya, we can’t continue to just copy and paste models from more developed infrastructure markets, we have to think of new ways to deal with how the undergirding system actually works and operates.

We give the internet away for free to consumers. How does that work if we all know that the internet isn’t free? After all, someone always pays.

The business model is an indirect one. We charge businesses for some form of digital engagement on our Moja platform (app downloads, surveys, or content caching), and the free internet to our consumers is a by-product of this b2b business model. Like everyone else, we thought we could do it with advertising at first. But we realized that our unique hardware capabilities allowed us some other options, since advertising is a poor option for all but a few of the biggest global tech platforms.

Today we’ve deployed 850 of the SupaBRCK’s running our Moja software into public transportation (buses and matatus) in Kenya and Rwanda. They’ve been quite successful with almost 1/4 million unique users monthly in just the first three months. We have both a tested and working technology platform, as well as product market fit. With unit economics that make sense, a growing user base, and a business model that works, we’re excited for the growth phase of the business. This next step means going nation-scale in each of these countries, and also determining our next market to enter.

It’s important that ordinary people across Africa and other frontier markets can stop thinking about the costs of the internet and don’t have to turn off their mobile internet on the smartphones that they already have in their pockets.

Once they know they can afford it, the way they use the internet changes dramatically. An internet like this is feasible today, and it’s a cheaper, faster, more distributed, and resilient one. It’s also being built from the ground up in Africa, where we’re close to both the technology and human problems, and have a better chance of building the right thing.

Thoughts and Lessons Over 5 Years

First, make sure it’s a big enough problem.
If you’re going to spend 5+ years of your life on something, make sure it’s something that matters. At BRCK we are creating the onramp to the internet for anyone to connect to the internet, and a distribution platform for organizations trying to reach them. If we succeed we only succeed at scale, which by its nature means that we’ve done something big and that it has made a large impact on people.

Second, figure out what to focus on.
When you start out it’s difficult to determine product market fit. We started with a wide funnel of possibilities for our technology, industries that we could target and consumer plays. Over time, we were able to narrow down what could work, and what we could actually do, to the point where we focused on this big “connecting people” problem. We did detour into education with our Kio Kit, which we still think is one of the best (if not the best) holistic solutions for emerging market schools – after all, it’s in places across Africa, as well as the Pacific Islands and as far as Mexico. However, it proved to be too costly for our bottom line to hold inventory, sales cycles are too long, and it was largely a product sale. When we realized that, we started to focus most of our efforts on the bigger underlying issue across all of the markets, which was affordable connectivity and our Moja platform.

Third, persistence trumps skill.
Building hardware is hard. It’s even harder doing it in Africa. The upside, however, is that you’re both closer to the problem and that, if you succeed in figuring it out, you have a good head start on everyone else. The process takes time, costs money, and there are people and organizations who don’t want you to succeed. It always takes longer than you want to get software working properly, or hardware built and reliable. We’ve often been faced by that same problem that plagues all venture backed companies in Africa, in that you have to do a lot of education to investors to even raise the capital, and then when you do, you get charged a premium for perceived risk. Partner organizations take resources and time to work with, and they don’t always come through on their promises. All of these things (and more) mean that the best ideas don’t always win in the market, because it’s those that push the hardest and longest that win.

Fourth, it’s the people you do it with.
If you’re going to be on a journey that takes a great deal of time, with intense pressure, and where success is not guaranteed, then you had better do it with people that you can trust, who you can work with, and it helps if you like them too. Throughout my work career I’ve been more fortunate than most (whether at Ushahidi, iHub, or BRCK), and this time is no exception. I get to work with a host of wonderful people; not just smart and talented, but also genuinely good human beings. It makes work a joyful challenge, not an exhausting chore.

So, to those back in the day who believed we could do this when it was just a sketch in my notebook, thank you Shuler, Kobia, Nat, and Juliana (and the rest of the team at Ushahidi). To our investors who have joined us in this dream of connecting and doing hard things, you’ve continued to step up and that has made this possible. Thank you.

To Jeff, Janet, Birir, Kurt, Barre, and Oira, thank you for sticking it out for all these years and stepping up to more leadership challenges as we’ve evolved. To Philip, Reg, and Kala, I want to thank you for making the impossible happen, time and again, each for more than 5+ years.

Crisis Stack: A microserver for disaster response teams

The heritage of BRCK is that we were born out of Ushahidi, which builds platforms for changing the way information flows in crisis and disasters events globally. It shouldn’t be a surprise then that we think a lot about how BRCK hardware can help extend the ability of disaster response teams around the world.

BRCK+Pi - new design concept for production

BRCK+Pi – new design concept for production

1: A Rugged Microserver

With the recent development of the BRCK+Pi, which marries a RaspberryPi + hard drive + 8-hour battery, to the BRCK in a simple package (full specs below), it gave us a chance to think through what could happen beyond just connectivity in tough environments. After all, with this extra computing power it turns the device into a remote microserver, where you can cache content locally and do stuff even when in an offline mode.

In short, the BRCK+Pi allows not just the standard BRCK connectivity, but now also the ability for content and computing in a small, rugged form factor that can be used anywhere.

2: Software for Disaster Response Teams

This allows us to provide a stack of disaster-related software that could be loaded onto the device. The goal being to have a core software stack available on BRCK+Pi devices to humanitarian response organizations globally. The purpose being to help speed recovery after a crisis, making first responder’s lives more efficient and making technology work where it normally doesn’t.

While anyone who makes these tools can put some time into making their tool work on the microserver, I was thinking to list out the full grouping that came out of a discussion on the CrisisMappers network recently, and then prioritize them into foundational tools that could be made into a “package” to download onto your own BRCK+Pi and which would help the broadest set of disaster responders. I asked the following questions:
   

  • What ideas do you have that would fit on BRCK+Pi?
  • Which problems could this help with?
  • Are there any software packages that you’d find valuable in the Crisis Stack?

3: What Goes in the Box?

First pass on this is about a set of basic tools that we can think of as a “core package”. We had an open call with members of the CrisisMappers community where we talked about the types of software needed and use cases for it. The initial tool list looks like this, though the repository is open on Github and can be changed, added to, or just plain branched in the future:

  • OSM tiles (Light) – (Ex: Haiti Browser)
  • OSM Sync – Make a mark on a map served off the BRCK+Pi and synchronize with OSM API occasionally
  • SMSsync – Use the BRCK wireless modem to allow for text messaging, rewritten to be native on the BRCK Device
  • LDLN – An inexpensive, distributed local data hub, with mobile apps to address damaged communication infrastructures after natural disasters
  • Sahana Eden – A suite of tools designed specifically for organizations during disasters, including organization registry, project tracking, asset tracking and more.
  • Cellular Coverage Mapping – Find a tool to report the signal strength measured if connected to cell network to contribute to existing project (see: http://www.ebola-cellular-map.resudox.net/)
  • Etherpad Lite – The most basic and simple communications tool we know of
  • Image sharing tool – Still to be determined, but could be BitTorent Sync for file management (protocol for local sync, not for normal torrenting activities)

Secondary applications to consider are:

ONA – http://ona.io/
Enketo – https://enketo.org/
FrontlineSMS -http://www.frontlinesms.com/
Ping – http://pingapp.io/
DragonForce – http://www.drakontas.com/
Ushahidi – http://ushahidi.com
WordPress – http://wordpress.org
Flickr or YouTube Sync
Wiki  – Gollum, Dokuwiki or Mediawiki
VPN service

4: Getting Stuff Done & How You Can Help

An idea, once outlined, is good but not enough. Now it’s time to build something. This week the BRCK and Ushahidi teams have been working on getting the basic libraries to run the “core package” onto the device. We’ve also setup a Github repo for Crisis Stack that is open for others to join. Beyond that, the team is getting Etherpad and Ushahidi 2.x working on the device.

Mikel Maron of Open Street Map was on the call and is helping to get the OSM tiles working.
Praneeth Bodduluri of Sahana also joined us and is helping to make Sahana Eden available.
I’m in contact with the LDLN team and we hope to have them also contributing to the core package.

We’re on the way to getting an alpha of Crisis Stack out by mid-February, we need the community in the disaster response space to help to make it happen.

If you’re a software engineer and would like to be involved, check out the repository and get involved with one of the projects that’s being put on the device.

If you’re a first responder, let us know what we is really needed on the device. We’ll need testers on this front as well, of course, but that won’t happen until we get some basic items working on it.

—————————————————–

BRCK+Pi specs

BRCK+Pi - initial working prototype

BRCK+Pi – initial working prototype

• IP51 water and dust ingress protection
• Dimensions: 132mm (5.18 inches) by 72mm (2.82 inches) by 45mm (1.77 inches)
• Native Raspberry Pi network connectivity when connected to BRCK
• Input voltage 5 – 18V, 0.1 – 3A charge current.
• Solar compatible charging
• Over voltage and reverse polarity protected inputs
• Dual USB connection to BRCK+Pi for Keyboard or Mouse (500mA)
• Mini-HDMI Video Out
• SDXC support (up to 2TB of SD storage), normally ships with 16GB
• BCM2835 SoC
• 4GB native storage (upgradeable to 500GB with extra cost)
• 512MB RAM
• 3.7V 8,000 mAH battery
• Can be preconfigured with Raspbian, but compatible with any Raspberry Pi distribution.
• Connects to the BRCK by stacking underneath, screws on for security


You can find the BRCK specs here.

BRCK Nile Expedition Redux

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…?)

How the Internet of Things Can Help Save Our Rivers

You’ve been hearing a lot about our recent trip to Uganda, and we’re not through yet! In addition to working with Hackers for Charity, connecting schools around Jinja, and wirelessly controlling underwater robots, we wanted to explore the IoT side of the BRCK, too.

MRTR in Pelican

A number of people we’re working with are keen on using BRCKs to remotely connect sensors and other objects to feed data back over the internet. Some of the uses we get most excited about are around conservation, ranging from tracking vultures to locate poaching kills to remote weather stations in the savannah.

Two projects we know of, Into the Okavango (http://intotheokavango.org) and the Mara Project (http://mara.yale.edu ; http://mamase.unesco-ihe.org), are deploying networks of sensors to monitor entire ecosystems. By tracking water quality throughout the Okavango Delta in Botswana and the Maasai Mara in Kenya, each hopes to improve our understanding of these fragile environments, and by publicly posting the data (as well as pictures of their own expeditions) on their websites, they hope to inspire further appreciation amongst those who may never get a chance to visit these amazing places in person.

When we first started talking about going to Uganda, home to the source of the White Nile flowing out of Lake Victoria, we knew we had to find a way to get out on the river and try our hand at collecting environmental data via the BRCK ourselves. It just so happens that Paul, one of the expedition team members, was a river guide for seven years in Colorado before coming to Kenya, and had found out about an expedition being planned by Pete Meredith down the Karuma to Murchison Falls stretch of the Nile.

Paul Rowing

This stretch is home to the largest concentrations of hippos and crocodiles anywhere on the Nile, and has been rafted less than 10 times in history, only once commercially. It’s home to some of the biggest, most terrifying whitewater in Uganda – a country known for big, terrifying whitewater. Uganda is also a country that is industrializing fast, with hydroelectric power stations playing a key role in meeting fast growing energy demand.

All these new dams mean that rivers in their natural flow are disappearing quickly. The Bujagali Dam near Jinja covered 388 hectares in reservoir, flooding several miles of pristine whitewater. A new dam under construction near Karuma threatens to seriously affect the wildlife that concentrate downstream, and the Murchison stretch may no longer be runnable after 2018. With almost 85% of Uganda’s population unable to access electricity, the case against building more dams is hardly clear cut, but it does mean the time to learn from, share, and experience some of the most unique ecosystems along the Nile is running out.

As a team of gadget-headed engineers, we figured a good first step would be to have an affordable, reliable platform for collecting and disseminating information about these ecosystems. While the BRCK itself runs on an Arduino compatible microprocessor, we included a blank AVR chip with direct access to the pins through a dedicated GPIO port on the back. In Jinja, our lead RF engineer Jackie quickly soldered up a pH and temperature sensor kit to a GPIO MRTR, and off we went.

Jackie Soldering

After much debate, and despite being a generally adventuresome and outgoing bunch, the Murchison stretch proved to be a bit too much for some of our team, most of whom had never rafted before. (Mention the word “Murchison” around here and even the local guides have to suppress a shudder of anxiety. Pete is still planning an expedition for springtime, for those with a serious bug for adventure and not too tight an attachment to this world – http://www.nalubalerafting.com/expedition.html.)

Instead, we opted to run the 30 or so kilometers of the Nile north of Jinja with Nalubale Rafting. Our goal was to get far enough away from “civilization” to test both the BRCK’s connectivity and the GPIO setup. The first day on the water, we hit five major Class IV/V rapids, including a three-meter tall, nearly vertical drop.

Big Hit 1

Big Hit 2

Drone_boats

Drone_hole

BRCK Flag

Big hole

Drop_top

Drop_middle

Drop_bottom

Along the way, we plugged in our MRTR and dipped our sensors into the water. Not being hydrological engineers ourselves, we weren’t quite sure what to do with any data we might collect, but we did learn some valuable design lessons around using the BRCK with the GPIO port (such as the need for a tighter connection between the MRTR case and the BRCK’s body). Ultimately, the hardware worked great, but some work remains on the software side to view our data on the web. We’ll be working on these tweaks and incorporating them, along with a means to visualize data fed through the port, into future updates.

Sensor dip

After a hard day of paddling (and no small amount of swimming, only some of which was involuntary) we found ourselves at our campsite overlooking the river. It’s hard to imagine what this place will be like in 10 years. There’s nothing quite like eating dinner around the campfire, away from the constantly connected buzz of the city to make you appreciate the stillness of the wild.

Campfire

As an expedition tech company, believe me, we get the irony. We still believe sharing these places before they disappear is the best chance we have for preserving them. There are far too many people who will never get to raft the source of the Nile, but we hope we can build a platform through which many more can experience it, if only vicariously.

Sunset

Expedition 2014 – Exploring Edtech on the Water

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!

BRCKs in Schools – Part Two

BRCK in Kawangware

Those of you that have been following our blog for a while know that a number of our partners work in the education technology sphere. Today, we went back to a school in Kawangware that we first visited in April with eLimu, a Kenyan edtech startup that introduced a tablet program to help primary school students prepare for their exams.

(Read the original post at: http://brck.com/2014/04/our-problem-is-internet-on-brcks-in-schools/#.VBbj3UtGzwI)

When asked how the tablets were working back in April, the school’s headmaster Peter told us, “The tablet program works very well, our problem is internet.” The school had a WiFi router/modem installed in the office, where a reasonably high-speed cable connection was available, but they were unable to get the signal in the classrooms. To use the tablets, students had to gather outside near the small office to get a strong enough connection. When the weather was bad or the sun was too bright, the tablets couldn’t be used.

Several days ago, Peter’s school got a BRCK. By running an Ethernet cable from their modem to the BRCK, they now have internet access in three classrooms. They can use the tablets when it is raining, when the sun is hot and bright, or even when the power goes out thanks to the BRCK’s battery and 3G failover. Today, the students were watching a video about the Mau Mau uprising in Kenya in the 1950s.

In Africa, it often seems that relatively small things derail big plans. Tablets can’t be used due to the sun’s glare, routers are rendered useless by voltage spikes and power outages. By addressing some of these small issues, we hope the BRCK can play a part in bringing bigger plans to fruition. We’ll bring you further updates from Peter’s school as they continue to try out new ways of learning from the worldwide web.

— — —

Want to get involved? BRCK and eLimu are looking to scale up by connecting 50 schools to the internet and providing them with tablets for learning. We also want to develop a caching system on the BRCK that could cut the cost of providing the same content to multiple tablets from ~$3 per student to less than $0.10.

We’re looking for someone who can help fund this project, so if that’s you, let us know!

“40% of the world is on the internet” and other 2014 stats

The ITU has just put out a new report showcasing some astounding numbers on general internet penetration, mobile broadband (wireless) use, and how the developing world compares to the rest.

[2014 ICT Facts and Figures ITU (1.7Mb PDF download)]

A couple of the interesting statements and figures

  • Internet user penetration has reached 40% globally, 78% in developed countries and 32% in developing countries. 2014 growth rates in developed countries remain at a relatively low, at 3.3% compared with 8.7% in developing countries.
  • In developed countries, mobile-broadband penetration will reach 84%, a level four times as high as in developing countries (21%).
  • Mobile-broadband penetration in Africa reaches close to 20% in 2014, up from 2% in 2010

Global active mobile broadband subscriber growth

Global active mobile broadband subscriber growth

  • Almost 7 billion mobile-cellular subscriptions worldwide – The developing countries are home to more than three quarters of all mobile-cellular subscriptions.
  • Fixed-broadband growth is slowing down in developing countries.
  • Almost 3 billion people (40%) are using the internet.

Percentage of individuals using the internet, by region, 2014

Percentage of individuals using the internet, by region, 2014

  • In Africa, almost 20% of the population will be online by end 2014, up from 10% in 2010.
  • 2013/14 growth rates in the developing world will be more than three times as high as those in the developed world (12.5% growth compared with 4%)