<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by David Boclé on Medium]]></title>
        <description><![CDATA[Stories by David Boclé on Medium]]></description>
        <link>https://medium.com/@bcldvd?source=rss-862fc5fa5f0a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*D2IQzuvuHHYXzLlH.png</url>
            <title>Stories by David Boclé on Medium</title>
            <link>https://medium.com/@bcldvd?source=rss-862fc5fa5f0a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 16:31:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@bcldvd/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Finastra’s developer portal : More than just APIs]]></title>
            <link>https://medium.com/finastra-fintechs-devs/finastras-developer-portal-more-than-just-apis-ec9be2e7b0b8?source=rss-862fc5fa5f0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/ec9be2e7b0b8</guid>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[how-to]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[fintech]]></category>
            <dc:creator><![CDATA[David Boclé]]></dc:creator>
            <pubDate>Tue, 28 Jul 2020 16:18:03 GMT</pubDate>
            <atom:updated>2020-07-31T12:48:10.941Z</atom:updated>
            <content:encoded><![CDATA[<h3>Finastra’s developer portal : More than just APIs</h3><p><a href="https://developer.fusionfabric.cloud/">Finastra’s Developer Portal</a> gives developers the power to use complex and specific financial functionalities to create applications.</p><p>In a <a href="https://medium.com/finastra-fintechs-devs/create-an-application-on-finastras-developer-portal-d90ef266cafb">previous article</a>, we’ve detailed how to create an application using APIs only. Today, we’ll focus on the other building blocks that you can find in our Developer Portal. We fundamentally think that a Developer Portal should not only be an API Gateway. This is of course very useful, but it’s not enough. You need a platform !</p><p>These are the fundamental building blocks that we believe are necessary in a future-proof Developer Portal :</p><ul><li>APIs</li><li>Events</li><li>SPIs (Service Provider Interface)</li><li>Data partnering</li></ul><p>Let’s dive into each and explain why they matter !</p><h3>APIs</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/988/1*jsjK2BkC27q_oWndJdeObw.png" /><figcaption>Abstract illustration of an API call between a Fintech (left) and a Bank (right)</figcaption></figure><p>No need to explain what an API is for developers reading this article. As for the rest of you, think of it as a request-response type of situation. Somebody asks for information, creates a request, and information comes out of the system through a response.</p><p>An example of that is Monotto, which created APIs on our Developer Portal for Fintechs to use. Have a look at their success story in this short video :</p><p><a href="https://www.fusionfabric.cloud/resources/partner-stories/monottos-robosave-automating-financial-stability-through-artificial">Monotto&#39;s RoboSave: Automating financial stability through artificial intelligence | FusionFabric.cloud</a></p><blockquote>TLDR; APIs are the way to get informations out of a system and put informations into a system</blockquote><h3>Events</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1004/1*3TLiIpwcsj1jOw1dr7z9vA.png" /><figcaption>Abstract illustration of an event being triggered from a Bank (right) and dispatched to Fintechs (left)</figcaption></figure><p>An event is kind of the opposite of an API in terms of flow, as it originates from a process that is running inside of the Bank’s core system.</p><p>Eventing is used to push information from the core banking system to anybody who is looking at that data. To be “looking at data” one would need to register/subscribe first to get notifications.</p><p>This eventing mechanism allows the subscriber to be informed in real time and do something about the event, but not necessarily to respond back to the bank.</p><p>Find an example below of an integration of events from FusionFabric.cloud, that was built on top of Salesforce Financial Services Cloud :</p><p><a href="https://www.finastra.com/solutions/lending/loan-origination/fusion-credit-connect">Fusion Credit Connect</a></p><blockquote>TLDR; You need events because you cannot see, know or react to things that are happening in a system private to you</blockquote><h3>SPIs</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/982/1*tR-4qL_kpANbGsYjeM0SLw.png" /><figcaption>Abstract illustration of a Bank (right) calling an SPI from a Fintech (left) during a process to potentially alter that process</figcaption></figure><p>SPIs inverse the relationship with APIs, but not the same way events do.</p><p>Basically, they allow for extension or change of behaviour of a system. Any of our product can define a place in their execution to call for an SPI. As a developer, you can provide an endpoint that you have developed to be requested upon the event is triggered.</p><p>Let’s take an simple example with Fraud Detection :</p><p>A developer has registered its SPI on a fraud detection event inside of a Payment Solution. A payment is being processed, and in place of using the core system’s way of checking for fraud detection, the bank is going to make a request to the SPI. In this way, the fraud provider would be able to return a fraud result, that the payment system would then use in the decision making in the rest of the process, ultimately leading to not processing the payment if the result leads to that conclusion !</p><blockquote>TLDR; SPIs are the way to extend or change the behaviour of already existing APIs.</blockquote><h3>Data Partnering</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/966/1*0VeyhPNfWT72UxTAqWoeHw.png" /><figcaption>Abstract illustration of a Dataset coming from a Bank (left) being consumed by a Fintech (right)</figcaption></figure><p>Data partnering solves the issue of providing large amounts of data <strong>securely</strong> to data scientists, to enable them to train Machine Learning models.</p><p>As a data scientist, coming across meaningful volumes of data to be able to train models is very hard.</p><p>As a bank, your data is gold, and you cannot allow it to be publicly accessible to anyone, but you would benefit from outsiders’ Machine Learning algorithms.</p><p>Finastra is trying to bridge the gap between banks and data scientists through an API like contract, where data scientists can require access to Datasets, seeing the format, and a sample of the data beforehand, and Banks can grant consent on an individual basis. Once approved, the data flows in a protected way, being point to point encrypted. Finastra actually never sees this data.</p><blockquote>TLDR; Data is mandatory to train a Machine Learning model</blockquote><p>Those are the four building blocks with which you can basically build anything ! Let’s see some examples of how to combine all of these together to create a great customer experience !</p><h3>Empathetic Banking</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U4uJC1xJhVXUEosp084k_Q.png" /><figcaption>Empathetic Banking user flow</figcaption></figure><ul><li>Customer walks in branch.</li><li>Cameras send an <strong>event</strong> to bank officer systems, retrieving customer’s history using <strong>APIs</strong>. AI systems retrieve <strong>data</strong> (Get Accounts) about the customer with insights on what products to offer customer. Trained from <strong>DataPartnering Data</strong> (Accounts, Transactions, etc…)</li><li>Intelligence is gathered from external systems using <strong>SPIs</strong> (Account Lookup).</li><li>After leaving the branch, IoT devices like the customer’s car and home provide follow-up by receiving <strong>events</strong> (Marketing) and invoking <strong>APIs</strong> (Offers).</li></ul><p><strong>Banking as a service</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pvuKklWF8vfEQIVjHFhDeg.png" /><figcaption>Banking as a Service user flow</figcaption></figure><ul><li>Bank creates new revenue stream as the engine for non-financial company SolarWorld that embeds financial services in its consumer app.</li><li>SolarWorld app does Loan Origination, KYC and Funding using <strong>APIs</strong>. SolarWorld provides fraud detection using <strong>SPIs</strong> in payment to make fast lending possible.</li><li>SolarWorld app can tailor offering to consumer using AI-based predictions thanks to <strong>data</strong> and to geo-location and uses <strong>events</strong> to make them pop up.</li></ul><p>That’s it for today !</p><p>I hope this was informative 🤗! If you want to go more in depth, go explore our Developer Portal :</p><p><a href="https://developer.fusionfabric.cloud/">FusionCreator Developer Portal</a></p><p>If you liked this article :</p><ul><li>Add some 👏</li><li>Share it</li><li>Follow our <a href="https://medium.com/finastra-fintechs-devs">Medium Publications</a></li><li>Try to make some apps using our <a href="https://developer.fusionfabric.cloud/">Developer Portal</a> &amp; <a href="https://design.fusionfabric.cloud/">Design System</a></li><li>… or only one of the above 😆</li></ul><p>Till next time !</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec9be2e7b0b8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/finastra-fintechs-devs/finastras-developer-portal-more-than-just-apis-ec9be2e7b0b8">Finastra’s developer portal : More than just APIs</a> was originally published in <a href="https://medium.com/finastra-fintechs-devs">Finastra Fintechs &amp; Devs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Demystifying financial applications creation]]></title>
            <link>https://medium.com/finastra-fintechs-devs/demystifying-financial-applications-creation-87bf1b7715e9?source=rss-862fc5fa5f0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/87bf1b7715e9</guid>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[innovation]]></category>
            <dc:creator><![CDATA[David Boclé]]></dc:creator>
            <pubDate>Mon, 15 Jun 2020 21:11:01 GMT</pubDate>
            <atom:updated>2020-06-15T21:11:01.117Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*L9vbAN1ihDPZq8hn" /></figure><p>I’ve been working at Finastra for more than 5 years now, and I’m baffled when my colleagues from outside the financial industry think I’m working on a Nuclear Fusion Reactor, joking at how complex this sector is.</p><p>Granted, Finance is a broad sector and security is at the core of everything we’re doing. But it’s also a time-proven field, where most of the big issues have been solved, and now patterns emerged out. I strongly believe that nowadays, with the move to Open Banking, anyone could make an application for a Bank or Financial Institution, with or without Financial background. The hardest part really is knowing the regulations of each country 🙈.</p><p>That being said, don’t expect that by the end of this article, you’ll be a financial genius (I, for one, am sure not 😆). What we’re going to do here is create a sample Corporate Banking application:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VxwqAVfgSIbHHf6ysSwHrQ.gif" /></figure><p>You’re all familiar to Retail Banking : it’s what you use, probably on a daily basis, to check your bank accounts, transfer money to friends and family and so on. Simply put, Corporate Banking is the same, but applied to a Company. Whether you’re a multinational or a startup, you still need to check your account balances and transfer money. But you also have needs that are not required for an individual such as processing payments <em>from</em> or <em>to</em> in batch (for example : paying employees or making a request for payment of a monthly membership), Trade and Supply Chain Finance and so on…</p><p>This article will not go in depth to see how the supporting sample app was done step by step, but rather detail some of the milestones and big concepts. Of course, you’ll be able to check at anytime the entirety of the source code on Github:</p><p><a href="https://github.com/fusionfabric/ffdc-sample-corporate-webapp">fusionfabric/ffdc-sample-corporate-webapp</a></p><h3>Register an application on Developer Portal</h3><p>As defined in our <a href="https://developer.fusionfabric.cloud/ffdc-documentation/appendix-glossary.html#glossary-application">glossary</a>, an application is “<em>The custom collection of </em><a href="https://developer.fusionfabric.cloud/ffdc-documentation/appendix-glossary.html#glossary-api"><em>APIs</em></a><em>, </em><a href="https://developer.fusionfabric.cloud/ffdc-documentation/appendix-glossary.html#glossary-spi"><em>SPIs</em></a><em> and/or </em><a href="https://developer.fusionfabric.cloud/ffdc-documentation/appendix-glossary.html#glossary-dataset"><em>Datasets</em></a><em> that you create through the </em><a href="https://developer.fusionfabric.cloud/ffdc-documentation/join-app-wizard.html"><em>Application Creation Wizard</em></a><em> on FusionCreator.</em>”</p><p>Do not confuse it with a <a href="https://developer.fusionfabric.cloud/ffdc-documentation/appendix-glossary.html#glossary-client-app">client application</a> or end user application, which is what you are probably using everyday. It could be a web application, mobile application or even an application for an IoT device such as a car or a TV ! And all of them would be referenced under the <a href="https://www.fusionfabric.cloud/"><em>FFDC</em></a><em> application</em> as they would all be using the same set of APIs, SPIs and Datasets!</p><p>If you are not familiar with how to create one on our <a href="https://developer.fusionfabric.cloud/">Developer Portal</a>, here is a great summary:</p><p><a href="https://medium.com/finastra-fintechs-devs/create-an-application-on-finastras-developer-portal-d90ef266cafb">Create an application on Finastra’s Developer Portal</a></p><p>Once you have your client ID and secret pair ready, let’s use them in a server side application.</p><h3>Authenticate</h3><p><a href="https://developer.fusionfabric.cloud/">Finastra’s Developer Portal</a> uses OAuth 2 to authenticate, which is nice, as it’s a standard, and a lots of libraries have been developed for different languages and frameworks since its inception.</p><p>The different values you would be required to provide to such libraries would be the following:</p><ul><li><strong>Client ID</strong>: <em>detailed in the previous section</em></li><li><strong>Client Secret</strong>: <em>detailed in the previous section</em></li><li><strong>Issuer</strong>: <a href="https://api.fusionfabric.cloud/">https://api.fusionfabric.cloud</a></li><li><strong>Scopes</strong>: List of scopes required by your chosen APIs. In the case of the one we selected previously, there was no scopes so it would be empty</li><li><strong>Reply URL</strong>: The url to return to once the authentication flow is finished, at dev time this would be something like <a href="http://localhost:3000/">http://localhost:3000</a></li></ul><p>With this, you’ll be able to delegate the login page of your application to FFDC and eventually, to the financial institution that will be using your great software!</p><p>While working locally though, you will see the following login page, from the <em>Sandbox tenant</em>:</p><figure><img alt="Finastra’s Sandbox tenant login page" src="https://cdn-images-1.medium.com/max/1024/1*AV3qU5V9Sm7bvfgPdab4kA.png" /><figcaption>Finastra’s Sandbox tenant login page</figcaption></figure><p>Use one of the following pairs of credentials to log in :</p><ul><li>ffdcuser1:123456</li><li>ffdcuser2:123456</li></ul><p>What we did in our sample app is to use a module for OIDC (OpenID Connect) that we created internally and provided publicly for the community.</p><blockquote>Confusingly, OAuth2 is also the basis for OpenID Connect, which provides OpenID (authentication) on top of OAuth2 (authorization)</blockquote><p>This module’s documentation can be found below:</p><p><a href="https://github.com/fusionfabric/finastra-nodejs-libs/blob/develop/libs/oidc/README.md">fusionfabric/finastra-nodejs-libs</a></p><p>This module is basically a wrapper around <a href="https://github.com/panva/node-openid-client">openid-client</a> library, which is OpenID certified.</p><p>It is to be used with the <a href="https://nestjs.com/">NestJs</a> framework, which we like to use internally as it’s robust and very scalable for server-side applications. Yet the point we want to make here is not to say that everyone should use NestJS, we’re not trying to spark a technology debate. <strong>Use what you need for your use case ! </strong>But if you are already using NestJs, we thought it could interest you 😉</p><h3>Query for data</h3><p>So you have successfully authenticated yourself, and the result of this process gave you an <a href="https://developer.fusionfabric.cloud/documentation/appendix-glossary#glossary-access-token">access token</a>. With this, you are now able to query the aforementioned endpoints and retrieve data!!</p><p>Let’s circle back to our API, and say we would like to query the first endpoint, listing the accounts. Only thing to do is to make an HTTP request to <a href="https://api.fusionfabric.cloud/corporate/channels/accounts/me/v1/accounts?accountContext=ViewAccount">https://api.fusionfabric.cloud/corporate/channels/accounts/me/v1/accounts?accountContext=ViewAccount</a> and adding an “<em>Authorization</em>” header with “Bearer ${TOKEN}”, replacing ${TOKEN} with the value of your access token of course!</p><blockquote><strong>Bearer authentication</strong> (also called <strong>token authentication</strong>) is an <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Authentication">HTTP authentication scheme</a> that involves security tokens called bearer tokens. The name “Bearer authentication” can be understood as “give access to the bearer of this token.”</blockquote><p>Theoretically you could save the access token on the front-end, to enable the possibility for your SPA to make such request and target the APIs directly.</p><p>We would strongly argue against doing so as you should never trust your front-end (EVER).</p><p>A more secure way to query the APIs would be to keep the access token on the server, and have it be a proxy for doing the requests. Through a session or other mechanism to identify who is making the request, the server would automatically add the bearer token as authorization header to required requests!</p><p>Your front-end is not exposed but it can still retrieve data!</p><p>Pseudo code from the client would look like this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/90cf8696a68d34a46cd02d8341aa127f/href">https://medium.com/media/90cf8696a68d34a46cd02d8341aa127f/href</a></iframe><p>Once again for the NestJs users out there, we come to the rescue :</p><p><a href="https://github.com/fusionfabric/finastra-nodejs-libs/blob/develop/libs/proxy/README.md">fusionfabric/finastra-nodejs-libs</a></p><p>This module is a wrapper around the popular library <a href="https://github.com/http-party/node-http-proxy">node-http-proxy</a>. It will be looking for a user object (standard with <a href="https://github.com/jaredhanson/passport">passport</a>) on the request, and assign the access token to the authorization header !</p><p>On top of making the requests to the APIs from the server and not the front-end, in some use cases, you would be tempted to use technologies such as <a href="https://graphql.org/">GraphQL</a> to retrieve your data.</p><p>We’re not suggesting to use it ALL THE TIME, again, <strong>use what you need for your use case</strong> 😉. But if we take the <a href="https://developer.fusionfabric.cloud/api/corporate-accounteinfo-me-v1-831cb09d-cc10-4772-8ed5-8a6b72ec8e01/docs#operation/getAccountsForCustomerUser">Accounts Balances &amp; Statement API</a>, using aggregation on the backend is justified !</p><p>Indeed, the endpoints are resource oriented, and information is segregated by design.</p><p>When retrieving a list of accounts, you’re not retrieving the balances of those accounts. You can also get a list of the balances, but then you won’t get the account informations other than its ID. Getting the informations/balance/statement for one account is decoupled as independent calls. Which is a good pattern, you only query for what you need.</p><p>But the drawback is that your front-end will make 1 request for the list plus <em>n*2</em> requests per account information and statement to display. Which if you simply want to display 4 accounts, would require 9 separate requests from your front-end.</p><p>Using technologies like <a href="https://graphql.org/">GraphQL</a>, you could write a query such as the one below and have those 9 requests be done on the server and only one request would ultimately come from the client :</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/71f5715fd573e2c603f73ae89d9dd35c/href">https://medium.com/media/71f5715fd573e2c603f73ae89d9dd35c/href</a></iframe><p>Besides the obvious gain in front-end logic, not having to aggregate the data, you would gain a lot of load time because making a backend-to-backend request will always be more performant than frontend-to-backend !</p><p>Additionally, you would be able to re-use this in your mobile application, and be even more performance savvy by requiring a subset of all the information through specifying only the fields you need in your request. Every bit of information saved matters when developing for mobile 😉</p><blockquote>If you’re not familiar with the concept of BFF (Backend For Frontend), I would advise reading <a href="https://medium.com/tech-tajawal/backend-for-frontend-using-graphql-under-microservices-5b63bbfcd7d9">this article</a></blockquote><h3>Use Finastra patterns for UI</h3><p>So you can now log in and retrieve data. Let’s talk about molding this data into a formidable UI!</p><p>Like every major player out there, Finastra has been creating its own Design System.</p><p>If you’re part of a big company, you would have your own Design System as well. If that is not the case, or if you’re curious about how we do things, have a look at this article:</p><p><a href="https://medium.com/finastra-fintechs-devs/quick-peak-into-finastras-design-system-3504664228e7">Quick Peak into Finastra’s Design System</a></p><p>As you can see, the big difference is that we focus on Financial components that play hand in hand with the data from our Developer Portal.</p><p>On top of that, through our experience of app making, we carved out UI patterns to easily make the best choices of how to layout your application!</p><h3>Closing words</h3><p>Lots of concepts were tackled here, and it would seem that my point of demystifying complexity was lost in translation, but on the contrary : from all the concepts I went through in the articles, none require financial knowledge or background. Most (if not all) of those concepts are industry standards and used or heard of by 2020 web developers.</p><p>Through our Developer Portal and our Design System, we at Finastra are trying to hide the business complexity of creating an application, leaving you with only the technical skills to hone to be the next billion dollars Fintech unicorn!</p><p>Now that you fully understand the basics, you can go ahead and explore the rest of what Finastra offers regarding Corporate Banking:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XVkXibOBcQotT9J_u30fag.png" /><figcaption>Available use cases for Corporate Banking on Finastra’s Developer Portal</figcaption></figure><p>If you liked this article:</p><ul><li>Add some 👏</li><li>Share it</li><li>Follow our <a href="https://medium.com/finastra-fintechs-devs">Medium Publications</a></li><li>Try to make some apps using our <a href="https://developer.fusionfabric.cloud/">Developer Portal</a> &amp; <a href="https://design.fusionfabric.cloud/">Design System</a></li><li>… or all of the above 😆</li></ul><p>Till next time !</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=87bf1b7715e9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/finastra-fintechs-devs/demystifying-financial-applications-creation-87bf1b7715e9">Demystifying financial applications creation</a> was originally published in <a href="https://medium.com/finastra-fintechs-devs">Finastra Fintechs &amp; Devs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Speed up heroku deployments when using Heroku Buttons]]></title>
            <link>https://medium.com/@bcldvd/speed-up-heroku-deployments-when-using-heroku-buttons-4d5be8eb0d27?source=rss-862fc5fa5f0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/4d5be8eb0d27</guid>
            <category><![CDATA[github]]></category>
            <category><![CDATA[heroku]]></category>
            <category><![CDATA[angular]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[deployment]]></category>
            <dc:creator><![CDATA[David Boclé]]></dc:creator>
            <pubDate>Mon, 08 Jun 2020 12:39:59 GMT</pubDate>
            <atom:updated>2020-06-08T12:39:59.054Z</atom:updated>
            <content:encoded><![CDATA[<p>This article serves both as a <em>Note to self</em> and tips sharing as this might be useful to not only myself. Also I’d be interested in getting different views about this method 😊</p><p>If you’re not familiar with <em>Heroku Buttons</em>, here’s a quick primer :</p><blockquote><a href="https://www.heroku.com/elements/buttons">Heroku Buttons</a> provide an easy way to get an app up and running quickly on the Heroku platform. Heroku Buttons are pointers to source code repositories that have been extended with a tiny file that determines how the code should be deployed and configured. Clicking a Heroku Button will initiate deployment of the app, provide an option to configure the app, and deliver the running app on the web.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_hwf6kxugqymqxJYCM8GNg.png" /><figcaption>Simplified flow of using Heroku Buttons — Credits <a href="https://www.heroku.com/elements/buttons">Heroku</a></figcaption></figure><p>What we want to achieve through using Heroku Buttons is to give anyone a usable demo of your software, as quickly as possible ! Indeed, on some occasions, providing a live-demo next to your code is not possible, as the application requires a bit of context before being buildable. Also, for the uninformed user to go the hassle of cloning the repository locally and following the build steps, he has to be already convinced that this is what he wants to use, which is not always easy to figure out without a proper demo.</p><p>So in the <a href="https://devcenter.heroku.com/articles/app-json-schema">app.json</a>, describing how the code should be configured and deployed, you are usually specifying a build step. What if I told you that you could skip that ?</p><p>Indeed, most of the applications nowadays are stateless and rely on external configuration, be it environment variables or secrets tied to the container. So in between two commits, the build step of a deployment would produce the exact same output. What if we produced this output beforehand and re-use it in all our deployments ?</p><p>That’s what I ended up doing in my latest usage of Heroku Buttons, in a sample application for <a href="http://developer.fusionfabric.cloud/">FFDC</a> :</p><p><a href="https://github.com/fusionfabric/ffdc-sample-corporate-webapp">fusionfabric/ffdc-sample-corporate-webapp</a></p><p>This repository contains a <a href="https://nx.dev/">Nx</a> monorepo with an <a href="https://angular.io/">Angular</a> frontend application and a <a href="https://nestjs.com/">NestJs</a> backend one.</p><p>Using the default <a href="https://elements.heroku.com/buildpacks/heroku/heroku-buildpack-nodejs">heroku buildpack for Node</a>, Heroku will trigger the build script defined in the package.json, in order to build the application. If a script called “heroku-postbuild” is defined, Heroku will use this one instead, so we’ll use that to call our script that will retrieve a previously built output of our application :</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ad9314c3266a4b5936d496ff85274ffb/href">https://medium.com/media/ad9314c3266a4b5936d496ff85274ffb/href</a></iframe><p>Without going into too much details, my script was relying on a previously set <a href="https://github.com/fusionfabric/ffdc-sample-corporate-webapp/blob/master/.github/workflows/build.yml">Github Action</a>, that builds the app(s) and publishes the dist as an artifact, allowing me to retrieve this artifact and use it in my deployment !</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/772762bf85690b69e95b34b3af08f5c8/href">https://medium.com/media/772762bf85690b69e95b34b3af08f5c8/href</a></iframe><p>This script downloads and unzips the output of the build in a matter of seconds, whereas building the application lasted for nearly 2 minutes !! 2 minutes saved per deployment is a big gain, and takes you one step closer to having curious people engaged with what you’re building !</p><h4>Bonus tip for Angular 9+ developers : Skip Ivy post-install</h4><p>If you’re developing in Angular 9 and forward, you know that upon installing your node dependencies, Ivy is creating entry points for each of the modules, to enable faster build time afterword. Since we’re not building anymore, this post-install phase doesn’t make sense anymore during our deployments.</p><p>What I ended up doing was creating another script to launch while executing the post-install script which looks like the following :</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/6cb66222e53ec5b14caa4ff720d39c55/href">https://medium.com/media/6cb66222e53ec5b14caa4ff720d39c55/href</a></iframe><p>Basically, I’m looking for an environment variable that is only set during deployment on Heroku (in heroku’s app.json). If that variable exists, I do nothing, otherwise, it means I’m on my local machine, and I’ll execute the regular post-install command from the Angular Compiler (ngcc).</p><p>In conclusion, to speed up your deployment, think smart and think about the necessity of each of the steps of your deployments. Do they really have to be done for every deployment ? Or can we rather make this step once elsewhere and rely on the generated output in each of our deployments ? 😎</p><p>Have a look at the repository where I implemented this to have the full picture :</p><p><a href="https://github.com/fusionfabric/ffdc-sample-corporate-webapp">fusionfabric/ffdc-sample-corporate-webapp</a></p><p>If you liked this article :</p><ul><li>Add some 👏</li><li>Share it</li></ul><p>Till next time !</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4d5be8eb0d27" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Quick Peak into Finastra’s Design System]]></title>
            <link>https://medium.com/finastra-fintechs-devs/quick-peak-into-finastras-design-system-3504664228e7?source=rss-862fc5fa5f0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/3504664228e7</guid>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[how-to]]></category>
            <dc:creator><![CDATA[David Boclé]]></dc:creator>
            <pubDate>Mon, 08 Jun 2020 07:36:01 GMT</pubDate>
            <atom:updated>2020-06-08T07:36:01.198Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oUkaRxI1JnaE_hu-gUPjnQ.png" /><figcaption><a href="https://design.fusionfabric.cloud/">Finastra’s Design System</a></figcaption></figure><p>Like every major player out there, Finastra has been creating its own Design System. If you’re part of a big company, you would have your own Design System as well. If that is not the case, this article would be of interest to you, and as a primer, I would suggest this nice <a href="https://uxdesign.cc/everything-you-need-to-know-about-design-systems-54b109851969">read</a> on Design Systems.</p><p><a href="https://design.fusionfabric.cloud/">Finastra design system</a></p><p>Finastra’s Design System gives access to resources for both <a href="https://design.fusionfabric.cloud/get-started/designers">designers</a> and <a href="https://design.fusionfabric.cloud/get-started/developers">developers</a>.</p><p>For the latter, we provide 2 themes, one for <a href="https://github.com/fusionfabric/finastra-design-system/tree/master/themes/power-bi-theme">Power BI</a> and one for <a href="https://github.com/fusionfabric/finastra-design-system/blob/master/themes/angular-theme/README.md">Angular Material</a>, as well as some <a href="https://github.com/fusionfabric/finastra-design-system/blob/master/libs/angular-components/README.md">business widgets for the Angular Framework</a>.</p><p>Regardless if you’re an Angular developer or not, we try to always provide documentation that could be useful for anyone. Let’s take an example at the <a href="https://design.fusionfabric.cloud/components/data-visualization">Data Visualization documentation</a>:</p><p>On one hand, we provide <a href="https://design.fusionfabric.cloud/components/data-visualization?tab=dev">developer documentation</a> that would help Angular developers use our widgets; but on the other hand, we also provide a <a href="https://design.fusionfabric.cloud/components/data-visualization?tab=design">designer documentation</a>, where we explain what kind of chart to choose depending on the use case. Once again, we’re always circling back to using what you need for your use case 😉.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OtTRkxgIxVDmuTOGFS9vPA.png" /></figure><p>One of the specificity of our Design System is that we are producing widgets that are specific to the financial industry.</p><p>Let’s take a look at <a href="https://design.fusionfabric.cloud/components/card">our cards</a>. Cards are present everywhere nowadays, yet when browsing our documentation, you can see specialised cards for business use cases such as this one below :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tnuOR6x5hTWKnhtPiFpSTg.png" /><figcaption>Example of a card to represent a bank account</figcaption></figure><p>One of the things we are hard at work with is user experience out of the box. On top of great looking widgets, we’re trying to give tools for developers to craft a great experience with low-code investment.</p><p>An example of that would be that we expose skeleton equivalent of a widget next to the widget itself.</p><p>If you take a look at this sample of code below :</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a0471eb80cc1fb049ee348fcaa5b268d/href">https://medium.com/media/a0471eb80cc1fb049ee348fcaa5b268d/href</a></iframe><p>While the accounts are not loaded yet, we display some skeletons of the accout-card widget in place of the actual list of accounts. Doing so, the user gets a feel of what the interface will look like and the perceived speed will be much better, hence improving the overall experience</p><p>You can see it for yourself in action here :</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fstackblitz.com%2Fedit%2Fuxg-account-card%3Fembed%3D1%26file%3Dapp%252Ffds-demo.html%26view%3Dpreview&amp;display_name=StackBlitz&amp;url=https%3A%2F%2Fstackblitz.com%2Fedit%2Fuxg-account-card%3Ffile%3Dapp%252Ffds-demo.html%26view%3Dpreview&amp;image=https%3A%2F%2Fc.staticblitz.com%2Fassets%2Ficon-664493542621427cc8adae5e8f50d632f87aaa6ea1ce5b01e9a3d05b57940a9f.png&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=stackblitz" width="745" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/22c19f996becb5ecdd8ac0af249a10bb/href">https://medium.com/media/22c19f996becb5ecdd8ac0af249a10bb/href</a></iframe><p>This is a nice development pattern that we hope you will use across your applications; but let’s now talk about UI patterns !</p><p>At the time of writing, we currently expose 3 patterns :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R-5PUqt3-VeSA8WEc0QwYw.png" /><figcaption>Finastra Design System patterns</figcaption></figure><p>Let’s have a look at the first one : g<a href="https://design.fusionfabric.cloud/patterns/global-navigation">lobal navigation</a>, since we used it in our sample application!</p><p>Put simply, the global navigation pattern is an aggregation of 3 main parts :</p><ul><li>Toolbar</li><li>Side-navigation</li><li>App content</li></ul><p>But it has a profound impact of the structuring of your application :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pPNXR6O6qwfLAwPsHpsWTA.png" /></figure><blockquote>This kind of structuring echoes with <a href="https://micro-frontends.org/">micro-frontend</a> architecture. If this topic interests you, I would suggest <a href="https://www.youtube.com/watch?v=fl6F-f454to">this video</a>.</blockquote><p>In action, it results in the following :</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fstackblitz.com%2Fedit%2Fuxg-theme-launch-page%3Fembed%3D1%26view%3Dpreview&amp;display_name=StackBlitz&amp;url=https%3A%2F%2Fstackblitz.com%2Fedit%2Fuxg-theme-launch-page%3Fview%3Dpreview&amp;image=https%3A%2F%2Fc.staticblitz.com%2Fassets%2Ficon-1d2450aadcf984376236c23cd2ab0ba231ddd1d85c9b72990ed2ede5b4974d1b.png&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=stackblitz" width="745" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/42df7623963add7d8afb4637eee0673b/href">https://medium.com/media/42df7623963add7d8afb4637eee0673b/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fstackblitz.com%2Fedit%2Fuxg-global-nav%3Fembed%3D1%26file%3Dapp%252Fapp.component.html%26view%3Dpreview&amp;display_name=StackBlitz&amp;url=https%3A%2F%2Fstackblitz.com%2Fedit%2Fuxg-global-nav%3Ffile%3Dapp%252Fapp.component.html%26view%3Dpreview&amp;image=https%3A%2F%2Fc.staticblitz.com%2Fassets%2Ficon-664493542621427cc8adae5e8f50d632f87aaa6ea1ce5b01e9a3d05b57940a9f.png&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=stackblitz" width="745" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/dcb3523b98611984072128ed644ac89e/href">https://medium.com/media/dcb3523b98611984072128ed644ac89e/href</a></iframe><p>Using this pattern across your suite of products would result in an harmonized experience when your customer go from one application to the other.</p><p>A parallel I like to make is with the Office suite from Microsoft : Switching from Outlook to Powerpoint seems seamless because the overall structure/shell of the application is the same. Inner content and primary color being the only change to notify the user of this context switch !</p><h3>Auto dark mode</h3><p>One last nugget of knowledge that I want to pass on, as it gets a lot of traction and popularity these days : dark mode!</p><p>Finastra’s Design System implemented dark mode from the get go, and enabling it for your application would be as simple as that :</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/bde16f018ba685b6eea9e4e70b3f3c35/href">https://medium.com/media/bde16f018ba685b6eea9e4e70b3f3c35/href</a></iframe><p>See the full integration below :</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fstackblitz.com%2Fedit%2Fuxg-dark-mode%3Fembed%3D1%26file%3Dstyles.scss%26view%3Dpreview&amp;display_name=StackBlitz&amp;url=https%3A%2F%2Fstackblitz.com%2Fedit%2Fuxg-dark-mode%3Ffile%3Dstyles.scss%26view%3Dpreview&amp;image=https%3A%2F%2Fc.staticblitz.com%2Fassets%2Ficon-664493542621427cc8adae5e8f50d632f87aaa6ea1ce5b01e9a3d05b57940a9f.png&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=stackblitz" width="745" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/a4ef9f45a4dafa61de2a3c403b772542/href">https://medium.com/media/a4ef9f45a4dafa61de2a3c403b772542/href</a></iframe><p>That’s it for today !</p><p>I hope this was informative 🤗! If you want to go more in depth, go explore the website :</p><p><a href="https://design.fusionfabric.cloud/">Finastra design system</a></p><p>If you liked this article :</p><ul><li>Add some 👏</li><li>Share it</li><li>Follow our <a href="https://medium.com/finastra-fintechs-devs">Medium Publications</a></li><li>Try to make some apps using our <a href="https://developer.fusionfabric.cloud/">Developer Portal</a> &amp; <a href="https://design.fusionfabric.cloud/">Design System</a></li><li>… or all of the above 😆</li></ul><p>Till next time!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3504664228e7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/finastra-fintechs-devs/quick-peak-into-finastras-design-system-3504664228e7">Quick Peak into Finastra’s Design System</a> was originally published in <a href="https://medium.com/finastra-fintechs-devs">Finastra Fintechs &amp; Devs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Create an application on Finastra’s Developer Portal]]></title>
            <link>https://medium.com/finastra-fintechs-devs/create-an-application-on-finastras-developer-portal-d90ef266cafb?source=rss-862fc5fa5f0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/d90ef266cafb</guid>
            <category><![CDATA[finance]]></category>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[how-to]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[developer]]></category>
            <dc:creator><![CDATA[David Boclé]]></dc:creator>
            <pubDate>Mon, 18 May 2020 13:48:12 GMT</pubDate>
            <atom:updated>2020-06-05T08:52:06.407Z</atom:updated>
            <content:encoded><![CDATA[<h3>Register an application on Finastra’s Developer Portal</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4NOctKvUXGubM0QL9tndTQ.png" /><figcaption><a href="https://developer.fusionfabric.cloud/">Finastra’s Developer Portal</a> — <a href="https://developer.fusionfabric.cloud/explore/solutions">Solution Catalog</a></figcaption></figure><p>If you haven’t yet watched the different videos about <a href="https://www.youtube.com/watch?v=L_G3CZsQCiM">discovering our Developer Portal</a> and <a href="https://www.youtube.com/watch?v=ZenkpjFcsmo">Building an Application</a>, you can take some time to do so, or continue reading this article!</p><p><a href="https://developer.fusionfabric.cloud/">Finastra’s Developer Portal</a> gives developers the power to use complex and specific financial functionalities to create end user applications. Those functionalities are exposed through the form of <a href="https://developer.fusionfabric.cloud/ffdc-documentation/appendix-glossary.html#glossary-api">REST APIs</a>, which is an industry standard.</p><p>You can easily browse all those APIs here : <a href="https://developer.fusionfabric.cloud/explore/apis">https://developer.fusionfabric.cloud/explore/apis</a></p><blockquote>Using the filters on the left, you can quickly find what you’re looking for !</blockquote><p>You can also choose to explore from a Solution point of view : <a href="https://developer.fusionfabric.cloud/explore/solutions">https://developer.fusionfabric.cloud/explore/solutions</a></p><p>This layout gives you a view of a business solution, which is basically a grouping of several APIs to achieve one or many use cases.</p><p>As an example, we’re going to work with Corporate Banking, and more specifically, with Accounts Balances &amp; Statement. If you tried to find it by yourselves in our catalog, you should have arrived on this solution : <a href="https://developer.fusionfabric.cloud/solution/real-time-account-balances-and-statement">https://developer.fusionfabric.cloud/solution/real-time-account-balances-and-statement</a>.</p><p>As you can see, at the time of the writing, 1 API is present, but you can check our <a href="https://trello.com/b/hyZaWKPj/finastra-open-apis-roadmap">public roadmap</a> to see when we’re planning on adding more 😉</p><p>Let’s click on <a href="https://developer.fusionfabric.cloud/api/corporate-accounteinfo-me-v1-831cb09d-cc10-4772-8ed5-8a6b72ec8e01/docs">the API</a> and analyse together what we’re seeing :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4ptNFjm7Oghetb-gbgE_xA.png" /></figure><p>Under “Authentication”, you can see that this API is following the OAuth 2 (1) standard and that the flow will be <a href="https://developer.fusionfabric.cloud/ffdc-documentation/oauth2-grants.html#oauth2-auth-code-flow">authorization code</a> (2).</p><p>You also have informations regarding the authorization and token URLs as well as the required scopes to use this API, in this case, none.</p><blockquote>If you’re not familiar with OAuth 2, I strongly suggest <a href="https://www.youtube.com/watch?v=996OiexHze0">this video</a> which explains it really well, “in plain english” as they say 😊.</blockquote><p>Scrolling down or clicking on “Accounts” on the left will show you the following :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kuHEdSkV3-ivtnzgdsLl8A.png" /></figure><p>We are now getting in the specifics of this API, and reviewing it’s endpoints, which in layman’s terms are the indications about how you access a resource.</p><ul><li>On the left, you can see the list of endpoints, with their methods (GET/POST/PUT/DELETE). This API contains 5 of them which are only using the GET method, enabling you to retrieve data but not add, modify or delete data.</li><li>On the center, we’re displaying the relevant parameters that the endpoint in question can require, as well as the different responses types.</li><li>Finally on the right, you get a collapsible/expandable JSON that describes a sample of the returned data for each response types.</li></ul><p>Note that clicking on the endpoint path on the right side will display the full path :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/946/1*HGL0R3u0lSxUBYqa-GX8mw.png" /></figure><p>Now that we have identified what we want to use and most importantly, what it will enable us to do, let’s actually use it !</p><p>The next steps will actually require you to have an account on Finastra’s developer portal, which you can do by signing up here : <a href="https://www.fusionfabric.cloud/sign-up">https://www.fusionfabric.cloud/sign-up</a></p><p>Go do that, I’ll wait for you in the meantime 😁</p><p>You’re back already ? Great ! Let’s get going by registering an Application !</p><p>As defined in our <a href="https://developer.fusionfabric.cloud/ffdc-documentation/appendix-glossary.html#glossary-application">glossary</a>, an application is “<em>The custom collection of </em><a href="https://developer.fusionfabric.cloud/ffdc-documentation/appendix-glossary.html#glossary-api"><em>APIs</em></a><em>, </em><a href="https://developer.fusionfabric.cloud/ffdc-documentation/appendix-glossary.html#glossary-spi"><em>SPIs</em></a><em> and/or </em><a href="https://developer.fusionfabric.cloud/ffdc-documentation/appendix-glossary.html#glossary-dataset"><em>Datasets</em></a><em> that you create through the </em><a href="https://developer.fusionfabric.cloud/ffdc-documentation/join-app-wizard.html"><em>Application Creation Wizard</em></a><em> on FusionCreator.</em>”</p><p>Do not confuse it with a <a href="https://developer.fusionfabric.cloud/ffdc-documentation/appendix-glossary.html#glossary-client-app">client application</a> or end user application, which is what you are probably using everyday. It could be a web application, mobile application or even an application for an IoT device such as a car or a TV ! And all of them would be referenced under the <a href="https://www.fusionfabric.cloud/"><em>FFDC</em></a><em> application</em> as they would all be using the same set of APIs, SPIs and Datasets !</p><p>Basically, we’re going to create an Application in the Developer Portal, that will describe which APIs we can use, so that when you publish your application and a Financial Institution wants to use it, they will see which APIs your application requires and grant you consent or not.</p><p>I like to make the parallel with using apps on your phone, you all have seen the “App XYZ would like to access the Camera” or the microphone or any other API that requires consent from the end user.</p><p>To allow this consent granting, our platform has to be aware of which APIs you are going to be using in your final application, hence this registration of what you may or may not be using.</p><p>Back to our potatoes !! If you revert to the <a href="https://developer.fusionfabric.cloud/solution/real-time-account-balances-and-statement">Solution page</a>, being logged in, you would be able to click on the “Create Application” button below :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GNCOLucVSVxVRMdKJy1trg.png" /></figure><p>Which would bring you to the Application creation wizard :</p><figure><img alt="Application creation Wizard : About" src="https://cdn-images-1.medium.com/max/1024/1*tY_yh8PAD_d_I4ptF6SdYg.png" /><figcaption>Application creation Wizard : About</figcaption></figure><p>After having given your app a fine name and description, you can head over to the building blocks by clicking “Next” :</p><figure><img alt="Application creation Wizard : Building Blocks" src="https://cdn-images-1.medium.com/max/1024/1*c17wkWABWOGADP30sL_KXw.png" /><figcaption>Application creation Wizard : Building Blocks</figcaption></figure><p>By default, all the APIs from the chosen solution will be preselected, but one more step is needed : you need to specify the <a href="https://developer.fusionfabric.cloud/ffdc-documentation/appendix-glossary.html#glossary-reply-url">Reply URLs</a> since our APIs are using a <em>Authorization Code</em> grant flow. For now, you can do as I did and put a wildcard “*”, but before going to production, be sure to set this up to an actual server that you and only you own 😉.</p><blockquote>Keen readers, might have noticed that you can add <a href="https://developer.fusionfabric.cloud/ffdc-documentation/appendix-glossary.html#glossary-spi">SPIs</a> and <a href="https://developer.fusionfabric.cloud/ffdc-documentation/appendix-glossary.html#glossary-dataset">Datasets</a> on top of APIs, but this will probably be for a future article !</blockquote><p>After blindly accepting the terms and conditions (which <a href="https://www.businessinsider.fr/us/deloitte-study-91-percent-agree-terms-of-service-without-reading-2017-11">90% of us do</a> 😳), you are greeted with a summary of all that you selected and upon clicking on “Create Application”, you will finally be able to see something like this :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hcDZQDaiMh7Ts5rGVh7TAQ.png" /></figure><p>As you can see, in the <em>API Credentials</em> section, you can copy the client ID and also generate keys. Let’s generate a secret key, that we will use as a client Secret :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eo8KbEnsOywM9KLBjaavzw.png" /></figure><p>Once you have your client ID and secret pair ready, you are set to use it in a server side application, and use the aforementioned APIs to build an awesome experience, and why not, be published on our store one day ? 😉</p><p>If you liked this article :</p><ul><li>Add some 👏</li><li>Share it</li><li>Follow our <a href="https://medium.com/finastra-fintechs-devs">Medium Publication</a></li><li>Try to make some apps using our <a href="https://developer.fusionfabric.cloud/">Developer Portal</a> &amp; <a href="https://design.fusionfabric.cloud/">Design System</a></li><li>… or all of the above 😆</li></ul><p>Till next time !</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d90ef266cafb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/finastra-fintechs-devs/create-an-application-on-finastras-developer-portal-d90ef266cafb">Create an application on Finastra’s Developer Portal</a> was originally published in <a href="https://medium.com/finastra-fintechs-devs">Finastra Fintechs &amp; Devs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Réseaux sociaux, buzz et mondialisation]]></title>
            <link>https://medium.com/@bcldvd/r%C3%A9seaux-sociaux-buzz-et-mondialisation-f98ea2667560?source=rss-862fc5fa5f0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/f98ea2667560</guid>
            <category><![CDATA[social-network]]></category>
            <category><![CDATA[french]]></category>
            <dc:creator><![CDATA[David Boclé]]></dc:creator>
            <pubDate>Sat, 03 Sep 2016 10:01:02 GMT</pubDate>
            <atom:updated>2016-09-03T10:01:02.935Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This post originally appeared on </em><a href="http://penseesdedavid.tumblr.com/post/47610953561/r%C3%A9seaux-sociaux-buzz-et-mondialisation"><em>Tumblr</em></a><em> the 10th of Apr 2013.</em></p><p>En regardant une affiche présentant la sortie mondiale d’une nouvelle série télé américaine, je me suis fait la remarque suivante : De plus en plus de séries bénéficient d’une sortie mondiale simultanée, ainsi que les films. Effectivement, il n’y a pas si longtemps, nous, pauvres français, devions attendre 6 mois avant la sortie d’un film américain en France ! Pourquoi ce revirement soudain ?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*DcWsuZ-6P0LBIr4h.jpg" /></figure><p>L’explication qui m’est venu en premier, est celle de l’engouement. En effet, une sortie mondiale, provoquerait un buzz beaucoup plus massif, car simultané dans beaucoup de pays, et donc beaucoup plus de personnes potentielle qui en parlent. Et le fait d’en parler, fait parler. Alors que si l’on lance un produit en 2013, pays après pays, le premier pays en parlera, mais quand le suivant en parlera, le premier aura déjà fini d’en parler, ou du moins en parlera beaucoup moins. C’est très schématisé, mais l’idée est là. <br>Tout ceci est facilité par l’avènement des réseaux sociaux. Grâce à ces derniers, le buzz est véhiculé à une vitesse incroyable, et sans prendre compte de la barrière géographique. Combien de fois, un fait anodin a tourné au buzz grâce aux réseaux sociaux ? Ceci n’est pas seulement vrai pour les séries télé ou les films, il est attrait à n’importe quel produit, marque, personnalité etc… Grâce aux réseaux sociaux, n’importe quel individu est à même de faire buzzer son produit facilement, et à travers le globe. C’est d’autant plus vrai pour les contenus dématérialisés tels que la vidéo ou la musique ! Connaissez vous beaucoup d’artistes qui lancent leur nouveaux albums pays après pays ? L’essor de cette dématérialisation géographique des magasins donc virtuels permets de lancer ce type de produits partout en même temps, et profiter d’un buzz massif grâce aux réseaux sociaux ! Le seul élément bloquant au bon déploiement du buzz est maintenant le fuseau horaire :)</p><p>Cette réflexion amène à plus de réflexion, et n’hésitez pas à commenter à la suite de l’article pour donner votre avis, ou une suite sur mes idées !</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f98ea2667560" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Repas, Nutrition et “Food Intake”]]></title>
            <link>https://medium.com/@bcldvd/repas-nutrition-et-food-intake-4823ab13448f?source=rss-862fc5fa5f0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/4823ab13448f</guid>
            <category><![CDATA[french]]></category>
            <category><![CDATA[nutrition]]></category>
            <dc:creator><![CDATA[David Boclé]]></dc:creator>
            <pubDate>Sat, 27 Aug 2016 10:01:02 GMT</pubDate>
            <atom:updated>2016-08-27T10:01:02.536Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This post originally appeared on </em><a href="http://penseesdedavid.tumblr.com/post/47013127655/repas-nutrition-et-food-intake"><em>Tumblr</em></a><em> the 4rd of Apr 2013.</em></p><p>Toujours sur le sujet de manger bien, parlons aujourd’hui du nombre de repas, et de l’heure à laquelle nous les prenons.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*IRw8As2vB7IJqbbr.jpg" /></figure><p>Je ne sais pas pour vous, mais j’ai toujours été habitué à prendre 3 repas par jours plus un gouter, à des heures fixes. Midi pour le déjeuner, 16heures pour le gouter et environ 20heures pour le diner. Ce précepte qui m’a été inculqué dès mon plus jeune âge, m’est resté avec le temps, et j’ai une réaction inconsciente quand je vois midi ou 16h, j’ai faim. Le fait de voir ces chiffres me donne faim… Je me rends compte à présent de la gravité de la situation quand je vois ce qu’il est conseillé de faire, à savoir écouter son corps, et manger à sa faim, quand on a faim. Ce qui revient à prendre environ 5 repas léger au lieu de 3 gros repas.</p><p>En parlant de gros repas, à nouveau je fais l’opposé de ce qui est prescris. En effet, il est conseillé d’avoir une alimentation quotidienne “pyramidale”. C’est à dire que le plus gros repas de la journée aura lieu le matin, et le plus petit repas le soir. Or dans mon cas (et le cas de beaucoup de mon entourage), j’ai peu faim et rarement le temps le matin pour manger en grande quantité, et toujours pas le temps le midi. Ce qui résulte en un repas gargantuesque le soir, et qui me ballone toute la soirée et m’empêche même parfois de m’endormir rapidement, car trop ballonné.</p><p>En résumé, il me faut étaler mon “food intake” pour arriver à 5 repas par jour, réussir à sentir quand j’ai un creux, et me rassasier sans me remplir. Je ne dirais pas non plus sortir de table en ayant encore faim, mais savoir s’arrêter avant de ne plus pouvoir rien avaler. Si je pouvais aussi éviter les produits industriels, et néfaste à mon organisme. Mais pour l’instant je n’ai pas le temps ni l’argent, donc je choisi la facilité…. Je le regretterais surement plus tard.</p><p>N’hésitez pas à parler de votre conceptions des repas, de vos conseils, votre retour d’expérience :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4823ab13448f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Manger bien, manger vite]]></title>
            <link>https://medium.com/@bcldvd/manger-bien-manger-vite-5b6a1c0d27a0?source=rss-862fc5fa5f0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/5b6a1c0d27a0</guid>
            <category><![CDATA[french]]></category>
            <category><![CDATA[fast-food]]></category>
            <dc:creator><![CDATA[David Boclé]]></dc:creator>
            <pubDate>Sat, 27 Aug 2016 10:01:02 GMT</pubDate>
            <atom:updated>2016-08-27T10:01:02.449Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This post originally appeared on </em><a href="http://penseesdedavid.tumblr.com/post/43977159048/expertise-et-changement"><em>Tumblr</em></a><em> the 20th of Mar 2013.</em></p><p>“La restauration rapide connaît une croissance à faire pâlir d’envie toute l’économie française. Les ventes ont progressé de 4 % en 2012, et de 73 % depuis 2005” (<a href="http://www.lemonde.fr/economie/article/2013/03/18/la-france-paradis-du-fast-food-americain_1849813_3234.html">source</a>), et il est vrai que de plus en plus, nous nous tournons vers des solutions de facilité pour déjeuner, et même parfois pour diner.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*y-Hip4DqNHyYR-Pc.jpg" /></figure><p>Étant étudiant, je n’ai pas beaucoup de temps le midi pour manger, et peu de motivation le soir pour me faire à manger. Je me tourne donc assez souvent vers la solution de la restauration rapide pour manger. Je dois néanmoins avouer que j’aime le gout du fast food, et le prix influe beaucoup sur ma prise de décision. Si l’on veut manger correctement aujourd’hui, il faut y mettre le prix, et quand ce prix n’est pas de l’argent, c’est du temps… J’arrive à 19h chez moi le soir, et j’ai entre 30min et une heure de sport à faire, et si je veux avoir du temps pour faire ma veille perso, travailler ou me reposer un peu, je n’ai pas le temps de cuisiner…De plus, mon mono-feu ne permet pas de cuisiner dans de bonnes conditions :)</p><p>Réjouissons-nous néanmoins, car la France est l’un des pays ou la “legislation alimentaire” est la plus stricte au monde. En effet, un Big Mac est extrèmement différent en France qu’aux US. Pareillement pour le coca-cola. L’exemple qui m’a le plus marqué, est quand j’ai pris un McChicken au Japon, le poulet était du poulet frit entier, style KFC, mais extrèmement huileux, ce qui ne semblait gêner que moi là bas. Les grandes pontes de la restauration rapide doivent plier l’échine pour pallier aux règlementations imposées par l’hexagone. La viande doit être élevée en France, et dans de bonnes conditions, les aliments sont controllés, le lieu de travail nettoyé etc… Néanmoins, si les grand du Fast Food ont maintenant compris la leçon à force de perdre dans les tribunaux, je ne pense pas que le kebab du coin fasse attention à quelquonque règlementation, donc faites tout de même attention.</p><p>Tout ce blabla pour dire que l’on mange de plus en plus de restauration rapide, et que même si on aime ça au gout, et que c’est plus simple et moins cher, notre corps en pâti. Et comme ma mère le dit si bien “ton corps est un temple”, il faut en prendre soin. Essayez de faire le marché le dimanche matin, à jeun, comme ça la marche matinale vous fera du bien, vous aurez faim, et dépenserez ainsi beaucoup au marché, ce qui forcera à dépenser moins ailleurs !</p><p>PS : Comme vous avez pu le remarquer, j’ai changé de format quand aux diffusions. Il y aura dorénavant une seule diffusion hebdomadaire, à la place d’une diffusion quotidienne. Chaque nouvel article sera posté mercredi, à midi. Les Inspirational pics du samedi restent inchangées. J’ai pris cette décision, car je n’ai plus beaucoup de temps à consacrer à ce blog en ce moment, et je n’ai pas envie de faire des articles pour faire des articles, résultant en des posts non qualiteux (on peut dire inutiles…). Ce nouveau format est, je l’espère, non définitif et changera à nouveau quand j’aurais plus de temps à consacrer à l’écriture.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5b6a1c0d27a0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kamikaze et envie de vivre]]></title>
            <link>https://medium.com/@bcldvd/kamikaze-et-envie-de-vivre-e2a29c2da67d?source=rss-862fc5fa5f0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/e2a29c2da67d</guid>
            <category><![CDATA[french]]></category>
            <category><![CDATA[carpe-diem]]></category>
            <dc:creator><![CDATA[David Boclé]]></dc:creator>
            <pubDate>Sat, 20 Aug 2016 10:01:02 GMT</pubDate>
            <atom:updated>2016-08-20T10:01:02.174Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This post originally appeared on </em><a href="http://penseesdedavid.tumblr.com/post/45412657683/kamikaze-et-envie-de-vivre"><em>Tumblr</em></a><em> the 15th of Mar 2013.</em></p><p>Clôturons cette semaine de réflexion personnelle, par une analyse d’un de mes proches, qui est mon opposé à bien des niveaux.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*_wG87EV0v9p-d9zU.jpg" /></figure><p>En effet, un test de personnalité a révélé que cette personne était plutôt rentre-dedans et kamikaze. L’utilisation du mot kamikaze m’a surpris au premier abord, mais je comprends à présent son sens. <br>Nous partons tous les deux du principe que nous n’avons qu’une seule vie, mais nos interprétations diffèrent. Pour lui, il n’a qu’une seule vie, “Live it to the fullest” ou “YOLO”, il n’a qu’une seule chance pour rendre sa vie la plus intéressante qu’elle soit. Il ne laissera jamais passer une opportunité de rendre une seconde de son quotidien plus excitant. Les risques lui importent peu tant que le possible résultat est là. Il aime la vitesse, il n’hésitera pas à faire du 180km/h pour ressentir cette sensation de liberté, au dépends des risques potentiel de voir la fin de sa vie arriver dans l’instant.<br>Pour moi, je n’ai qu’une seule vie, à la moindre erreur, elle est finie. Je ne prends donc pas de risques inconsidérés. Chacune de mes actions est réfléchie. D’après mon collègue, je vie seulement à moitié. Le fait de vivre avec lui m’a permis d’expérimenter ce YOLO et cette prise de risque pour pimenter le quotidien. Cependant je suis à présent revenu à mes vieilles habitudes, je ne ferai jamais du 180km/h à moins d’être sur un circuit en ligne droite, ou sur des rails. Je ne prendrais pas de risques inconsidérés : j’ai encore trop à voir dans ma vie pour la voir se terminer prématurément.<br>Qu’en pensez vous, faut il vivre chaque instant comme si il était le dernier ? Ou alors faire en sorte de faire durer ces instants, aussi longtemps que possible ?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e2a29c2da67d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[L’auto psychothérapie par l’écrit]]></title>
            <link>https://medium.com/@bcldvd/lauto-psychoth%C3%A9rapie-par-l-%C3%A9crit-d186df73569e?source=rss-862fc5fa5f0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/d186df73569e</guid>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[psychotherapy]]></category>
            <category><![CDATA[french]]></category>
            <dc:creator><![CDATA[David Boclé]]></dc:creator>
            <pubDate>Sat, 13 Aug 2016 10:01:01 GMT</pubDate>
            <atom:updated>2016-08-13T10:01:01.443Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This post originally appeared on </em><a href="http://penseesdedavid.tumblr.com/post/45337766586/lauto-psychoth%C3%A9rapie-par-l%C3%A9crit"><em>Tumblr</em></a><em> the 14th of Mar 2013.</em></p><p>La raison principale qui m’a poussé à faire <a href="http://penseesdedavid.tumblr.com/">ce blog</a>, était le besoin d’écrire. Le besoin de libérer son esprit, de faire partager, de “mettre sur papier”, de poser ma marque. Néanmoins, je ne me suis rendu que plus tard que j’étais en train de faire une thérapie à travers ce blog, comme beaucoup de bloggeurs, et le fait d’écrire, sur soi et à soi est très intéressant.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*utTRS-IGZ-TjIjko.jpg" /></figure><p>Quel est le but d’une psychothérapiste ? Vous écouter, réfléchir, et vous indiquer les points que vous refuser d’entendre. Poser les bonnes questions et au bon moment au final. Se poser les questions ne permet pas souvent de se remettre en question, mais le fait que ce soit une personne autre que soit, ou son entourage proche permet ce déclic étrange. Je suis en ce moment en train de réfléchir si l’auto psychothérapie par l’écrit est une chose possible.<br>Le principe serait d’écrire sur soit, puis de se relire en pensant que l’on lit quelqu’un d’autre, en cherchant à questionner cette personne. “Pourquoi avez vous agi comme cela”, “Qu’est-ce que vous avez ressenti après cela” ? Petit à petit, on poserait des questions que l’on ne se pose pas quand on y pense simplement, car nous pensons très vite, et nous n’avons pas le temps de réfléchir correctement à une question pertinente à poser avant de penser à une multitude d’autres choses, quand le sujet nous est cher. Le simple fait de poser ces mots sur le papier et de se relire ensuite, permets de ne rien oublier à la fois quand on raconte, et à la fois quand on questionne.<br>Je n’ai pas encore essayé de pratiquer cette méthode précise sur moi par manque de temps, car il faudrait que je me dédie une bonne après-midi pour être tranquille, et être sûr d’écrire et questionner longuement, mais je pense que même si imparfaite, et complémentaire d’une réelle thérapie, c’est un moyen intéressant d’aller de l’avant, et de poser un regard extérieur sur soi. Car après tout nous vivons notre vie depuis nos yeux, nous sommes très subjectif quand à nous même. Un peu d’objectivité, de vue externe et de remise en question fait du bien à n’importe qui !<br>Quand à mon blog, le simple fait d’écrire, et de me relire (sur des articles personnels), me fait réfléchir, notamment vis à vis de mon attitude par rapport à celle d’autrui. L’écriture, qui est un acte bien plus lent que la pensée, permet une double réflexion par rapport à la parole ou la pensée. On soupèse les mots que l’on utilise, et l’on réfléchis beaucoup plus à ce que l’on écrit que ce que l’on dit. L’écrit est une force, tachez de l’utiliser à bon escient.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d186df73569e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>