digital services & platforms in API economy. PhD (3D printing Full-stack API Economy house – APInf Oy – apinf.com Get Control of Your IoT Cruisers Developer point of view
behind you? Oh crap! Could you ask if they have Phones? APIs Data How much can I trust these people? Could you tell me have they enjoyed MindTrek? Could you tell me all personal Details of everyone behind you?
➔ Multiproxy support ➔ Multiprotocol (SOAP, REST, Websocket, Stomp, CoAP, TCP, MQTT) ➔ Smart City platform - FIWARE ➔ APItalists – API strategy & smart city consultancy ➔ Standardized API value chain automation – APIOps community Full-stack API Economy house Finland (Tampere), India, Ukraine and Brazil Tampere, Helsinki, Budapest, Atlanta (GA), Copenhagen...
– APInf Oy Data economy API economy Platform economy Data sets Function APIs Developer eXperience Data APIs Partner APIs Internal APIs Markets Scalability
on app developer ➔ Different needs, part of API productisement ➔ Provide business driven functional APIs + data APIs ➔ APIOps Cycles, offer easy to use high performance REST APIs + freetier ➔ Manage IoT data flow with light-weight open source solution ➔ MVP approach, expand to FIWARE platform, ecosystem
- Low barrier, sometimes makes more sense ➔ Quality, availability ➔ Open APIs – or free-tier, let them learn! ➔ Importance of API DX is not understood ➔ Limited access APIs - partner, commercial, governmental ➔ Platform Developer eXperience vs API DX
provide much needed functionality for developers and integrators. ➔Function APIs can save developers time when building their applications by providing needed functionality immediately, cost effectively, and with functionality that would otherwise be impossible without an API. More often another reason is not to give direct access to raw data for business reasons
APInf Oy Early adopters: gatekeepers, ”beta fine tuning” Innovators: skilled, participatory, window to future, ”forgiving” Mass: expect ease of use, self- service, performance, ”ruthless” Let them be
80% Provide functions over API, processed information, towards block programming Support application logic building – not just provide data Provide freetier (with APIs) – 3x more paying customers Use API management for outbound APIs - non-functional features Use standards based scalable IoT practices – data harvesting
Business and customer (developer) driven data sources ➔ CKAN for datasets ➔ Data and functional APIs ➔ Use flexible API management ➔ REST support for outbound eg for app builders ➔ IoT protocol support to manage device data flow ➔ Maximise easy onboarding ➔ Involve early adopters to minimise waste, maximise adoption and ROI (APIOps network, apiops.net)