Creating Datadipity
•Download as PPTX, PDF•
1 like•1,231 views
This is a presentation we gave at IoTa Internet of Things conference in San Francisco October 21st, 2014
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Creating Datadipity
Similar to Creating Datadipity (20)
More from Clickslide
Recently uploaded
Recently uploaded (20)
Creating Datadipity
- 1. Automation in API development. @Clickslide
- 2. We solve a BIG PROBLEM @Clickslide
- 3. We automate API integration @Clickslide
- 4. Most APIs aren’t easy to use. Source: "Ten Reasons Developers Hate Your API." by John Musser
- 5. And…. APIs have to be connected to a complex development stack. Source: "The Internet of Things Protocol stack – from sensors to business value" by Antony Passemard
- 6. And… There is a process to go from idea to implementation. Source: "Apps Development process." by Firsty Group
- 7. AND…?! ….there is testing and quality analysis to make sure everything is connected and works as it should. (Things still break)
- 8. Which means… Apps are delivered with limited features because API connections take too much time to connect, authenticate, mash and code! Source: "Ten Reasons Developers Hate Your API." by John Musser
- 9. Software Stack Client OLD WAY! (HTML/CSS /JavaScript) databases Servers Programming required Traditional proprietary software stack
- 10. Software Stack Using APIs OLD WAY! Server HTML5 Client databases APIs Programming required Traditional proprietary software stack leveraging APIs
- 11. Virtual API Stack NEW WAY! Client (JS/HTML5) APIs Programming required API Powered JavaScript Client
- 12. Virtualized API Stack with Datadipity Datadipity APIs NML.js Client Programming required No Programming required Front-end Only – JavaScript Everywhere THE NEW WAY!
- 13. Why APIs?
- 14. APIs are the backbone of… @Clickslide Connected Apps The Internet of Things Wearble Devices Wearable Devices Source: "Why should C-Level care about APIs? It's the new economy, stupid." by Fabernovel
- 15. Visit us here! Datadipity is compatible with over 10,000 APIs!
- 16. Datadipity reduces time to launch by promoting the “Virtualized API Stack” With a set of APIs in place, there is no need to architect complex distributed systems. 3rd party APIs are leveraged so that the architecture can be reduced to one code base. This reduces development time. Usability is much easier to maintain during beta release and user acceptance changes are easier to apply. Source: "Virtualized API Stacks." by Kin Lane
- 17. Our tools can accelerate a major portion of Programming and Development! Source: "Development Approach." by iLink Systems 50-80% FASTER! Let’s do more and go faster!
- 18. Datadipity API Datadipity is a service that handles all API connections. Datadipity provices Data Structuring for: – Reusable Logic – Reusable components – Plug-n-play intelligence with APIs – Focus on building beautiful front-ends – 100% JavaScript applications
- 19. What’s possible? Converts APIs into Software as a Service Channel partners for: • Extended Features • New Service Layers • Multichannel Partnerships The app shell and Datadipity API can provide beacon technology for: • Set-Top Boxes • Mobile Technology • Event spaces • Theme parks • Commercial Properties
- 20. Two main benefits of Datadipity: 1. A smaller code base 2. API services can be swapped out to maintain user requirements. Visit us here!
- 21. Datadipity leverages APIs to deliver complete products in a matter of hours! @Clickslide
- 22. Datadipity provides these web tools for automating API development: API Mashups UI templates API Distribution API Library
- 23. We want to significantly advance the Internet of Things Products Market. Cisco CEO: Internet of Things poised to be $19 trillion market Source: "Global business and government spending on IT products and services in US billions." by Forrester Supplier revenue contribution from IoT in 2020 is estimated at $309 billion. Source: "Gartner Says the Internet of Things Installed Base Will Grow to 26 Billion Units By 2020." by Gartner IoT install base will see a compound annual growth rate of 17.5 percent from 2013 to 2020 Source: "Internet of Things market to hit $7.1 trillion by 2020: IDC" by Leon Spencer
- 24. Business Model Delivery Method: 1) Cloud-based subscription model 2) On-premise gateway device 3) Partnerships. Customer Categories: 1) Tier 1 App Makers 2) IoT Product Makers 3) Data Integrators 4) API Stakeholders. @Clickslide
- 25. Proprietary Tech Patent: http://patentscope.wipo.int/search/en/WO2013032621 Business Development: We have won many software building competitions that demonstrate the power of our product. In the past 9 months we’ve won over $20,000 in cash and prizes. Inspiration and Experience: Gabriel is a founder of the technology and company. He was also an EIR @ Edinburgh University where he researched the concept of an Artificial- Intelligence-assisted Content Management Systems and how we could automate much of the website building process. We are applying this concept to all software development. Aaron is also a founder of the technology and company. He started building upon the concepts Gabriel had been exploring during his Residency at Edinburgh University. Aaron has been leading the technology and the concepts within it since its inception. @Clickslide
- 26. The API product Eco-pyramid Product Layer Automate API connections to a UI API Development Layer Services Layer APPS Leverages API services Infrastructure Layer
- 27. Competition Write Code API Stack Click buttons Datadipity is the first step towards a Full-stack CMS! Full stack Development
- 28. We have a beta! http://datadipity.com/register @Clickslide
- 29. How have we proven our tech?
- 30. We hack a lot. We’ve won over $40,000 this year at hackathons for building fully functioning products .
- 31. More on the horizon Through these hackathons we have created a number of partnerships for the the creation of connected products.
Editor's Notes
- Gabriel Ortiz, we began the R&D for this company in the United Kingdom and have recently relocated to NYC.
- We automated API integration because…
- Most APIs suck and this has always been the case, because different companies have different ideas for how to implement an API, API technology changes with innovation, but the overall problem in this scenario is integration.
- And integration goes deeper than just connecting a web service to a front end, there are many things to consider when creating a new software and many points where connections can break down.
- Because of all these possible breaks, there is a very long process to go from idea to implementation when you’re producing any software that requires a connection to a distributed system.
- And even with test-driven development, again, things can still break.
- That why v1 of an app can have a major reduction in planned usability.
- In traditional software development, teams would create a software stack of services for their project. Usually these will be running on multiple VMs or bare metal and load balanced between themselves and the client. In such a situation the client will most likely be rendered in the server and displayed using templates. Classic examples of this occur often in Ruby on Rails and PHP apps. Node.js has also gone this route due to its Asyncronous behavior. Which is great for PHP and Ruby on Rails developers to make the transition to Node.js. All connections and servers are written and abstraction layers between the data and client are managed in an MVC type of framework.
- This is a more traditional approach to API based development. Development teams will take a traditional approach but also leverage API technology in their server platform. The data and connections are typically coded in an MVC type of framework and the team will devise an Adapter strategy for managing all the different APIs required in the project.
- This is possible but very cumbersome. Writing a service layer for each API as well as managing redirects for every API authorization process will become unmanageable very quickly. There are some APIs that won’t support front-end authentication as well…
- The tools we use at Clickslide to develop software drastically alter the way one even approached software development. By isolating the code to just the client we not only simplify the way we work, but even the way we approach development has changed. I can offload most of the heavy lifting to APIs and then plug & play that intelligence into my UX via my business logic.