Viewing 2 posts - 1 through 2 (of 2 total)
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic.
Home › Forums › Ask the Flomies › Customized Flo device for sport
Tagged: Custom development, FloBLE
Hello,
we are looking to integrate NFC technologies into our sport mobile application.
FloJack or FloBLE seems very good match to our need for cost-efficient cross-platform device.
What options can you offer for customizing your device to our requirements?
Thank you!
Max
Hi Max, the FloJack and FloBLE designs can definitely be customized per your requirements. The costs involved will depend greatly on the level of customization needed. Changes to the outside mechanics are fairly easy whereas changes to the PCB layout or firmware functionality are relatively more time consuming. We would need to go through the details of what you need and estimate out the effort to get it done. At our current development rate is $150/hr (subject to change) we can then calculate the non-recurring engineering (NRE) cost involved. We typically charge an assessment fee of $1000 to go through this effort privately with each customer, however if you conduct the dialog openly on our Forum we can waive that fee. We believe in educating our community so as to promote innovation and action.
To give you a better idea on costs, the FloJack ran us roughly $300,000 to build from concept to production. The FloBLE reused a lot of what was done with the FloJack but added some new functionality as well, so the final NRE cost is looking to be about $100,000. We follow the Pareto principle of 80/20 when developing our products so these costs are well below market rates. This allows us to improve the solution over time as we better understand customer usage.
Once we can align the hardware to fit your needs, we will then execute a Flomio Developer relationship to formalize the partnership. Items like rebranding, support and paired programming options will be settled then. Check out this thread to learn more about the steps involved:
thanks,
Richard
You must be logged in to reply to this topic.