Knowledge Analysis – Tudor

On what topics do you need information to develop the final concept?

I will take Guohai’s UI research and make it into the actual music player that I worked on.

What sources will you use?

I will mostly use YouTube and StackOverflow for tutorials and troubleshooting.

 

Process

Given that I already implemented the functions needed for the UI, I need to familiarize with the UI-related tools in Android Studio. For that, I will watch tutorials that are relevant to the end goal.

 

Result

After watching this tutorial and troubleshooting various issues that have occured during the process, I managed to make the Android app look like the chosen UI.

Price matters

One of the main features of our product is the low price it can be bought at. I will try to make an accurate guess regarding the production costs for one piece, but there will still be room for doubt.

 

The main, physical components of the product are:

  • LightBlue Bean
  • LightBlue Bean components (buttons)
  • Outer shell
  • Bicycle support ring

 

  1. LBB – ~22€ – On the official site, 500 Beans can be purchased for $24/Bean, excluding transport.
  2. LBB components – <1€ – The buttons are very cheap, so they should not cost much.
  3. Outer shell – 3€ – for this part, there could be 2 options: moulded and printed.
  4. Bicycle support ring – <1€ – The same as the buttons.

The outer shell price is variable because of the two methods that can be used: moulding and printing.

Injection moulding is the industry standard, thus easily and pretty affordable on a large scale. Using a cost calculator, the estimated cost of one piece would be ~1,4€, when making 10000 pieces, as seen in the image below.

However, given the rise of 3D printing, this technology can be an alternate solution. One of our prototypes costed 30€ and had a total volume of ~250 cm^3. The model on which the costs above are calculated has a volume of ~60 cm^3. Some simple calculus shows the fact that it would cost ~4€/piece, which is more expensive than injection moulding. However, we could offer the possibility (via a license) for our customers to print the product with their own 3D printers, thus saving us production costs.

 

Total: 26€ + transport + putting everything together = ~30-35€/piece.

For 30€/piece, we would sell it to retailers at 50€/piece.

 

Alternatives:

1) No outsourcing

If we choose to keep the assembly process inside Europe, the LBB alternatives that I found are the Bluefruit EZ-Key, the RN42 Bluetooth Module and the HC-05 Bluetooth Module. The latter is not HID (Human interface device) capable. While the first two are HID capable and could represent an alternative for the LightBlue Bean, they need to be powered by an external battery pack, which would increase the space and prices needed for producing our product.

 

While cheaper than the LBB, the costs of both are still ~20€/piece.

 

 

2) Outsourcing

Another possibility would be buying and assembling everything in China and then transporting everything to the Netherlands. For the components, the prices would be the following:

Bluetooth module: 3€/piece

Mould injection: 0.16€/piece

Buttons + support: <0.5€/piece

TOTAL price of components: ~4€/piece

 

As far as transportation goes, there are two methods: sea shipping and air freight. In both cases, we assume that one piece weights ~100g and has a volume of ~150cm3.

 

1 Sea shipping

Transport cost for a Full Container Load (FCL) (~224 000 pieces): ~1400€

Various charges: ~750€

Total: Given that the production costs of 224000 pieces is 896000€ (significantly higher than the other expenses), we can approximate that transportation = ~4€/piece.

 

2 Air freight

The volume of 10 000 pieces = 1.5m3. At 100g/piece, the total weight is 1000kg. Taking a volumetric factor of 200, the volumetric weight is 1.5*200 = 300kg, thus the actual weight is applied in the calculations.

At a rate of 4.5€/kg, the total transportation costs are 4500€ / 10 000 pieces = 0.45€/piece.

Total: 4+0.45+0.5=5€/piece.

Product design progress #2

Concept

After analyzing the first draft, our product had to be redesigned.

The problems we had to solve were:

  • Placing the LBB inside the handle would take up too much space
  • The buttons are not visible with the current layout
  • The product is not sufficiently adjustable for other bike handles
  • The design is too hard to build with our knowledge

With this in mind, we chose to build our product on an existing mount for bicycle lamps. This already solves a view previous problems:

  • The device is easily adjustable
  • Buttons would be easily visible and reachable
  • The LBB can be placed inside with no consequences for the user comfort

Also with this we can maintain our goal of making a low budget product.

 

We bought this mount for a bicycle lamp in the store and we will use the mechanic for our product.

Clip

Layout

We will be using one type of bike for the prototype testing. The product will be placed over the right handle.

AttachingSpot

BasicLayout

 

Measurements

Before the technical design can be made, a number of measurements have to be done.

1. Attachment clip

ClipDimensions

 

 2.Object size

For safety reasons, the product needs to be out of the way for movement of the hand. For this I made some measurements of how large the object should be so it is not in the way, yet still comfortably usable.

Dimension.png

Technical design

Technical1

  • The device can be clicked into position with the bicycle mount

 

Tehcnical2

  • Batteries can be changed by opening the slide with the LBB inside

 

Sources

http://www.thingiverse.com/thing:410473

KNOWLEDGE ANALYSIS -Qu

Q: On what topics do you need information to develop the final concept?

A: I will be doing research on UI Interface for the app.

Q: What sources will you use?

A: I will be using Pinterest for research.

Background information

At this point of the development, we have established the connection between the light blue bean and our demo app as the first draft of our concept. Now it’s time to put the time in designing the user interface of the app, later on, I can give this designer to our teammate(Tudor) to do the coding according to this UI.

Functions

Before I start to design the UI, I need to know what function should be included in the interface, and what function should not be included in there.In this UI design, we will keep the interface as simple as possible. The reason for that is while the user is on the bike they don’t have the attention to handling too many functions.The following functions are included in the UI.
Play/ pause
Prev/ next
Volume +/-

Design Research

I have some visual research on Pinterest the result can be seen under this paragraph.

 

UI Final Result

UI