After the campaign, we will send you a form asking you to choose the modules and colour you like.

The main BLOCKS Core will have a 400 mAh battery which is double the size of Apple watch (205 mAh) and more than most other smartwatches on the market today.

Yes! Add $30 to your pledge for each additional Module and you can buy as many Modules as you like. You can even use the payment as credit for Modules that will be released in the future after the Kickstarter campaign.

We are working hard on making this possible but we can not guarantee it. If the campaign exceeds a certain threshold and we have the funds for it, we will make it available in the first iteration itself.

You Spoke, we listened!
We have reduced our shipping prices not just to the UK/EU but WORLDWIDE! It is now $11 to ship to the US and $15 to ship anywhere in the world!

Our manufacturing is in China and Taiwan and we will be shipping our devices from there. We want the shipping process to be as seamless as possible for our backers

Yes! Kickstarter does not have Paypal configured as a payment provider but our website does. Have a look at our Kickstarter campaign and when your ready to pledge, just visit the page below. You will still have the same rights as all our other Kickstarter backers and we will send you a personal confirmation after the campaign.
Please visit:
http://www.chooseblocks.com/paypal

The BLOCKS watch will come with a cable that can be connected by a proprietary connector to the Core of the watch. Additionally, we will likely provide a secondary cable that can be used to charge your extra battery modules individually.

BLOCKS will have a variety of apps on launch. These will cover all the basics such as notifications, activity tracking, calendar, smartphone camera control, call from phone, voice search, voice memos, maps, payments, alarm timer and environment tracking. And these are only the apps that are already confirmed.

We will also be working with third party software developers so that they can optimize their Android apps to work on your BLOCKS watch.

The Core has a 45 mm diameter and is approximately 11 mm thick.
The Modules are 30 mm wide and 6 mm thick.
We are iterating on the final production unit with our manufacturers, which will enable us to make it more sleek.

Wearables are highly constrained by space for electronics. Companies are having to compromise on the features that are packed into wearables that fits around the wrist. Unlike smartphones, wearables can offer a much larger array of features to choose from and a device that is about ¼ of the size.

In addition to a handful of features that currently preside in smartwatches, such as Bluetooth/WiFi to allow notifications, accelerometer for activity tracking, heart rate monitor and microphone, many other possible features are rarely present. There are only a few examples of watches that have one of the following: GPS, Long Battery life, Galvanic Skin Response (stress level) and Body Temperature (for athletes) or a camera. This however is only the beginning of what is possible with wearables. More specialized devices can hold extra storage for music, gesture control sensors, heart beat monitoring sensors (for authentication or medical monitoring), RFID cards for access or even a variety of gas sensors to be used by workers in industry.

BLOCKS performed a thorough survey of human wrist types - both in geometry and size. The watch can accommodate the majority of wrist sizes. The majority of wrists are 140mm-200mm in circumferences. BLOCKS has an ergonomic shape which is comfortable to wear in any configuration with a highly adjustable clasp.
Small wrist would comfortably fit 4 additional modules in addition to the Core of the watch and individuals with larger wrists could fit up to 5 modules.

Blocks runs on the modified version of latest Android operating system. It works with iOS 8 and above, on iPhone 4s and above. It also works with all Android 4.0+ phones including those from LG, Motorola, Sony, Samsung, HTC, Xiaomi and more.

BLOCKS will support both iOS and Android devices.

Over the past two years, one of our main priorities has been to make sure there will be a great app ecosystem to go with our modular technology. Hence our strategy has been always towards that.
Let's start with resolving some main concerns and questions.
First question you had was about the Module connection compatibility with iOS.
This is not a problem at all, since all the processing and gathering of data from the Modules and controlling them are done natively on the powerful Qualcomm processor within the Core. There is no intervention of the phone companion app, whether it is iOS or Android, it is irrelevant here and there is no problem.
Second, you had a question about iOS compatibility and how advanced this integration will be. We are sure you all know that iOS has some restrictions for interacting with the notifications for 3rd parties and Apple doesn't allow developers to access and respond to some notifications. These restrictions are the same for any non-Apple watch device, and even applies to Google's Android Wear, Pebble, or any other companion device. We will have the maximum possible integration that Apple would allow us (and any other non-Apple company!).
Hopefully, an increasing number of requests from third party companion devices and demand from iPhone users, will force them to give more permissions and integration options in the next iOS versions to Android Wear and BLOCKS.
Thirdly, the concern was the number of apps. Based on our extensive surveys, smartwatch users actually don't use that many apps on the watch and only use a number of high quality apps which help them do a specific task. These tasks are normally related to the relevant hardware sensor, e.g. heart rate measurement or fitness app which directly uses the data from the accelerometer and heart rate sensor.
Moreover, smartwatch users are always restricted by the lack of sensors, functionality and the slow and lagged loading of content from the phone to the watch. BLOCKS solves this issue by having native apps (natively on the main processor on the Core) so they will be very fast and responsive and also by having the main sensors on the watch as Modules rather than having them on the phone. E.g. for the GPS Module, since you can have it on BLOCKS as a Module, it will be much faster to gather data and much more reliable compared to having it on the phone.
Needless to mention, this enables you to use your BLOCKS even if you don't have your phone around.
As some of you have mentioned, BLOCKS is a great project on the hardware side and has numerous renowned hardware partners but may lack on the number of apps. The good thing is that these hardware partners are responsible for developing their respective apps as well for their Modules. E.g. payments app for the contactless Module, Navigation app for the GPS Module, etc. Over the past two years, we have had deep discussions with Google Android team numerous times and now we are working with Cronologics, a company which is founded by a number of ex-Google Android folks who were tired of the restrictions of Android Wear and wanted to build a better ecosystem for Android Smartwatches.
We strategically decided to use the optimized full Android OS, in order to make it easy for app developers. There has been even discussions with Google about the possibility of having Google Mobile Services and even moving to Android Wear if Android Wear reaches a point where it can support all the requirements we have for Modularity and hot swappable connections in the future.
Developing for the optimized Android on BLOCKS is much easier than developing for other platforms since it just needs the re-design of user interface from phone screen to our screen. Of course, we will not be able to convince all app developers on play store to develop for BLOCKS (nor a smartwatch needs every type of app), but our choice of operating system and easy MDK would make it easier to develop the ecosystem.

At the end of the day, the richness of an ecosystem is all about the partners and support and the capability of the project. BLOCKS is a very big project and since it is an open-platform relies on partners which will develop both the Modules and the respective apps for it. This is why we have seen this huge support and a big community over the past two years and the fact that as a small start-up we have been approached and are working with big names in this industry. Other than the current 1,500 registered developers, you wouldn't believe the wealth of emails we receive from large companies and software developers to be able to develop apps, even during this campaign.
We hope that you can keep on supporting us and understand that this kickstarter is the big start for us. If we can gather a large group of users at this point, this would make it much easier for us to later approach larger app developers and bring them on BLOCKS.

We considered offering 'dummy' Modules so that backers could select 1-2 functional Modules and the rest dummy Modules to save on costs. However, dummy Modules are not very price efficient as they still require circuity, power management, the microprocessor and connectors making them similar in price to the Extra battery Module. This is why we suggest backers to get extra battery Modules instead as they will be universally usable when your battery is low

Our idea is that the watchface will be something unique to you. This could be something simple, like your name or could be more personalized to show only the 'complications' you want (for eg, stopwatch, date, time, chronometer) or a photo of you. Depending on what most backers want, we will devise a solution that is best for everyone.