DEV Community: FabianBG

The DDD microservice with GO

FabianBG — Tue, 08 Sep 2020 19:06:59 +0000

Intro

Hi everybody, these last days I decided to star a base project with the basic folder structure and libraries to start easily a new microservice with GOLANG. Right now there is a lot of continuous change in the GOLANG environment so this project uses a specific tech stack but can be adapted to any tech stack due to the architecture of DDD which is an architecture that I think helps a lot to make more refactorable any project.

Tech Stack

Basically knowing that the arch gonna be Doman Driven Design I find the best suitable techs to apply this patterns to the project so at the end if you know about the current frameworks on the internet you should know (GOKIT)[https://github.com/go-kit/kit] as its definition is not a framework is a bunch of tools to develop microservices it supports a lot of advanced features like services discovering and circuit breakers. SO this is the main reason for me to choose this tech to develop this base project.
For the data persistence, I go for a mongo to keep a simple and versatile data model there is an official mongo connector for GOLANG so it is simple to make the decision of which library use.

Architecture

The chosen architecture will be Doman Driven Desing to keep the project well organized and very scalable.

Project

So there is the project it could be found on my GitHub page on clicking this link [https://github.com/FabianBG/gokit-base].

I hope it helps you to get into Golang and any comments about how to improve the code it is welcome.

Tech your computer to play chrome dino game

FabianBG — Mon, 25 May 2020 02:47:22 +0000

Intro

As an AI fanatic I decide to do a simple neural net to learn more about TensorFlow so I do a neural net which plays the offline chrome dino game, It a very simple approach than it is not the best and perfect but as a starter, point to learn AI, it is a funny way to do it.

The project

For the common AI learning agents actually exist a lot of playgrounds (like GYM [https://gym.openai.com/]) which simplify the way you interact with the game, the playgrounds can be paused and played frame by frame which is very helpful, it has a lot of useful data of each frame of the game such as rewards and game status. But For this I want to make it from a very scratch. So I choose to do it with the famous dino game.

The project is coded in Python3, to get the actual state of the game it takes screenshots of the chrome window and has a controller for the keyboard to trigger the keypress. It is not a deep reinforcement learning approach, it is more like a supervised approach because first of all I played the game to generate the data then this data is fed to the neural net and finally is used to play.

For the inpatients, the source code is on GitHub [https://github.com/FabianBG/dinoplayer-neuralnet]

Usage

First of all download the code and open google chrome on [crome://dino].

Then in the folder of the code execute the next command:

python3 main.py preview

It shows the preview of the area in which the code takes the screenshoots so move the navigator with the game to fit the preview.

When the screenshot area is set, use this command to generate the train data:

python3 main.py gen-data

To start recording data press the key i, and to stop key e, finally to save the data on the preview window press the key q.

It will generate a data-train.pkl file on the source. This contains the train data for your model.

Next step is to train the model, so just exec:
python3 main.py train

When all the train is done it saves a model.tf file which has the trained model.

Finally, to see how it does, execute
python main.py predict

And to start predicting press press the key i start the game and let the computer tries to do its best.

The net can be improved just modify the file model.py it has the net definition.

MIJO chatbot store site manager FINAL PART AND SUBMIT

FabianBG — Fri, 24 Apr 2020 21:48:19 +0000

MIJO chatbot store site manager PART 2

FabianBG ・ Apr 21 ・ 2 min read

#twiliohackathon #ecommerce #chabot #gatsby

What I built

I created a multi-static site manager for personal stores, managed through a chatbot. All the management of simple store such as create products, remove products and place orders it is done through message texts with a chatbot, it simplifies all the front end development and security because the bot is the only one who can access the API and as a developer, you just focus on the services.

As a customer you can create your own store with some products than you like to sell and all managed just by sending a Whatsapp text to the chatbot. No application installed just a text.

Inspiration

I decide to try this new approach because I think the chatbots have a lot of usages actually, in this case it can completely replace a complex UI and be as simple as an everyday action of sending messages. It simplifies the interaction with the machines and make more simple to use the new technologies for people that are not much into the tech.

What MIJO does

It can create a store site with a simple base Gatsby template and deploy a static site on the server, manage a list of products and handle the customer checkout sending a message to the owner telling him about the customer and his order.

Category Submission:

Exciting X-Factors is the main category of this project a good usage of the Twilio services to add a new way to manage an application with an AI assistant.

Demo Link

A sample of the app is deployed on development and very small server of my company, I am moving the app to a personal server with more reliable storage and getting the Whatsapp Bussiness account to go to production, right now as a demo I using this small server.

Main site:
[https://1.up-company.dev/]

If you want to try a demo join the Whatsapp sandbox let me a comment to give you the message to join my sandbox and give a try.

Showcase

Main page:

Create an store:

Add a product and update the site:

Generated site:

Place an order:

Link to Code

All the code is on [https://github.com/FabianBG/mijo-chatbot-store]

How I built it (what's the stack? did I run into issues or discover something new along the way?)

The main stack is NodeJS and Express for the compatibility with Gabsty which is the static site generator for the stores.
Over the Twilio integration, it was pretty simple all the info is in the documentation, right now the bot is very simple I want to improve it and add more languages support.

Next steps

I enjoyed the development and the idea is to keep working in this project adding more features and maybe more usages. Integrate a database to manage the store owner data and have more historic data to generate insights with it. Add more templates and improve the existing one.

Actually Twilio Autopilot juts support English which is a problem related to my location so I hope they add more support to other languages in the future.

MIJO chatbot store site manager PART 2

FabianBG — Tue, 21 Apr 2020 23:29:31 +0000

MIJO chatbot store site manager PART 1

FabianBG ・ Apr 19 ・ 2 min read

#twiliohackathon #ecommerce #chabot #mijo

Goals

Create the ExpressJS project DONE
Customize Gabsty Ecommerce template
Integrate with Twilio API
Improvements

Progress

This article covers the second and third goals, I refactored the project to organize better the code so I divided on domain and application. For the domain is all the business logic and for application all the endpoints.
The project has two kinds of endpoints Twilio and app.

Twilio endpoints expose:

Create store create a new gatsby site based on a template
Add a product add products to the Gatsby site
Updates store site Deploy the static site
Delete a product removes a product

App endpoints expose:

Place order which sends a message to the store owner with the details and contact info.

Gatsby theme

I customized the Gatsby site and it gonna be the first theme for the site, in the future I expect to add more themes.
The final result of the custom theme:

All the created sites gonna have this theme.

Twilio Integration

For the integration in the app I defined a folder that contains all the integration logic of sending a message through WhatsApp, and a body parse for Twilio chatbot requests.

I used the Programmable SMS and Autopilot services to generate a simple bot that can take some basic commands and send a request to the API.

The bot has an action for each endpoint:

I tested all with the Watsapp sandbox and exposing my app with Ngrok and all the integration is simple and very easy. All the info is in the documentation of Twilio.
The bot is very simple but does what I want with more time it can be improved and make more human-like.

I think the media handler for images gonna be a headache but it was pretty simple Twilio do the bigger part of handling the media and asking for it, the validation is done it too.

Next steps

All the core idea is implemented, so the next step is to deploy the app so I gonna dockerize the app and add some improvements and bug fixes.

MIJO chatbot store site manager PART 1

FabianBG — Sun, 19 Apr 2020 23:47:27 +0000

Intro

I decide to try this new approach because I think the chatbots are becoming more valuable becoming very good personal assistance. And this can be a new way to develop the front end of many services in the future.

What MIJO gonna do

It can create a store site with a simple base gatsby template and deploy a static site. When the customer checkout in the store it sends a message (through the chatbot) to the owner telling him about the customer and his order.

Tech Stack

The main stack is NodeJS because of the compatibility with Gatsby which is the static site generator for the stores. And has the SDK for Twilio. For the server and REST API manager the beloved ExpressJS.

Goals

I defined the next goals to end the project:

Create the ExpressJS project
Customize Gabsty Ecommerce template
Integrate with Twilio API
Improvements

Progress

I already have the NodeJS Express project generated and working on the customization of the Gabsty e-commerce template to support custom product management with son files and on the checkout, action sends data to the express server.

I chose [https://github.com/parmsang/gatsby-starter-ecommerce/tree/master/src] Gabsty starter for the store template I liked the minimalistic design (THANKS TO parmsang for this beautiful design), but for the site, It has to be customized to remove some functionality and add custom functionality to support the new way of managing the site.

A tricky part here is I want to reuse the node modules folder for the express project and the Gabsty generated sites because of the space consumption of having a lot of sites and each one with its owns node modules.

Next step

I have to make ExpressJS generate a new Gatsby site and publish it in a static folder, the endpoints to add and remove products and the checkout handler. So wait for the next update.

Add the CI to your project with Azure DevOps

FabianBG — Sat, 14 Mar 2020 01:32:03 +0000

DevOps

The DevOps stuff is everywhere right now, and as developer, it is important to known about it, actually it is more than a bunch of tools is a culture of automatization that you should develop in every project you made, so in this post, I am going to show a little example of a simple DevOps automatization.

So if you have a side project you can found a lot of tools to apply the DevOps philosophy, a lot of people use (CircleCI)[https://circleci.com/] or (TravisCI)[https://travis-ci.com/] which are pretty the same idea of create a script to automatize a flow defined by you.

I chose Azure DevOps (I gonna do a post for the other tools too) which allows you to have a private or public project by free, it can be useful if you don't want to have a public repository to apply a CI pipe, Azure DevOps can integrate with different source version control providers such as GitHub(Microsoft) and Bitbucket or if you want, you can use the Azure Repo tool integrated in Azure Devops.

PROJECT DESCRIPTION

For the project I gonna use a Github repo with a base project of micronaut-java[https://github.com/FabianBG/microservice_micronaut_base], the automatized process will be like:

push code to branch:

     => if branch updated
           => test
           => build
           => dockerize
           => push to DockerHub
           => use everywhere

Let's do it

First of all, we need a project to deploy so choose a project that you want to automatize, but be careful about the technology, sometimes the technology is hard to automatize or build. For this case I gonna use a Micronaut java project if you want to know more about it see this page [https://fabianbg.netlify.com/posts/micronaut--introduction-tutorial-article/] is an article written by me(when I started writing in Spanish
:P). This is a base project that connects to a Postgres database and exposes some REST services.

The second step is to create the test, build and dockerize scripts this gonna be the tricky part because it depends on the technology than you are using but actually a lot of technologies come with a helpful client which can do a lot easier the job. In the case of micronaut-java you have maven or gradle, if you use a more complex process in your build or test you should have to create a script in the root of your project folder to tell the pipe that executes the script to easily deploy your app.

The third step is an account in Azure Devops[https://azure.microsoft.com/es-es/services/devops/]:

Once you have the account, the next step is to create a project, you can choose if you want to have and private or public project so choose what is more useful for you.

After the project is created, you can see the dashboard of the project. There are a bunch of tools that can be helpful for a development like a Jira board of tasks, repos, pipes, tests and artifacts but the most important part is the repos and pipes.

Import a repo

Ok, now start the fun part, in this case, I want to have the code in azure repos too, for this reason, I have to sync with my existing repo on GitHub for this in the repo view I select IMPORT.

Note: It is not necessary to create an azure repo or import it, **you can define directly a pipe and connect to a repo (Bitbucket, GitHub, Subversion and so).*

I paste the repo URL and let Azure do the import, in the end it shows you the imported repo.

Create the pipe

Ok, so this far the project is on Azure Repos now and it is time to configure the pipe, in the pipelines section you can create a new pipe, first you have to choose the repo provider if you have you code in another repo and don't want to have two repos one in Azure and another on you preferred provider you can skip the import repo part if you choose a different provider than azure repos you have to give access Azure DevOps to your repo. Once connected with your provider you chose the repo and it is time to configure your pipe:

These are the templates with basic pipes configurations, I gonna define my own pipe so I choose the Existing Azure Pipeline File option. The pipe file gonna contain all the configuration to tell Azure how to run the project and for my project is the next configuration:

trigger:
- master

pool:
  vmImage: 'ubuntu-latest'

variables:
  imageName: 'fabianbg/micronaut-base'


steps:
- task: Gradle@2
  displayName: Test
  inputs:
    workingDirectory: '$(Build.SourcesDirectory)/base'
    gradleWrapperFile: '$(Build.SourcesDirectory)/base/gradlew'
    gradleOptions: '-Xmx3072m'
    javaHomeOption: 'JDKVersion'
    jdkVersionOption: '1.8'
    jdkArchitectureOption: 'x64'
    publishJUnitResults: true
    testResultsFiles: '**/TEST-*.xml'
    tasks: 'test'

- task: Gradle@2
  displayName: Build
  inputs:
    workingDirectory: '$(Build.SourcesDirectory)/base'
    gradleWrapperFile: '$(Build.SourcesDirectory)/base/gradlew'
    gradleOptions: '-Xmx3072m'
    javaHomeOption: 'JDKVersion'
    jdkVersionOption: '1.8'
    jdkArchitectureOption: 'x64'
    publishJUnitResults: true
    testResultsFiles: '**/TEST-*.xml'
    tasks: 'build'

- task: Docker@2
  displayName: Build and Push docker image
  inputs:
    containerRegistry: 'DockerHUB'
    command: buildAndPush
    repository: $(imageName)
    dockerfile: '$(Build.SourcesDirectory)/base/Dockerfile'
    tags: |
      $(Build.BuildNumber)

This pipe has three tasks, *the test task with gradle test, the build task with gradle build and docker build and push task *. Azure provides a kind of task templates to exec commonly tasks such as gradle and docker you just have to provide the basic configuration to each one, which in some cases are the access credentials to the service.

Save the pipe but not RUN THE PIPE YET, it has no service connection configured so it gonna thrown an error because it can not access the DockerHUB repo to push the image before the run it is necessary to configure the service connection.

Service Connections

A service account is a way to protect our credentials to access external services such as a private docker hub repository or a server, with this we AVOID TO PUT CREDENTIALS ON OUR CODE, so instead just put the service account name and Azure do the binding to the credentials.

To create a service account, at the left side of the dashboard click on Project Settings, and then on service connections, you can create a new one:

There I created a service account to DockerHUB with the name of 'DockerHUB', so use this name to define the access in the pipe.

Pipe automatic trigger

As it is defined in the pipe, I have a trigger with the master branch, so if any change is sent to master it gonna trigger the build and notify by email.

For testing purposes, you can do a change to the project then push to the master branch and see what it happens.

Note: Remember to push to the repo that you choose when you create the pipe if it is an imported one push to azure repos.

If everything is right the pipe executes successfully and will send you a notification to your mail.

As we can see the built image on my DockerHUB account.

Conclusion

Azure DevOps is an easy tool to apply some automatization to our projects it can be done in a private way for free, the pricing starts at the second project and for free it is a limit of execution run time of the pipes.

The hardest part of automatization a project is not the CI pipes is the project itself as we can see if we use tools that help us like micronaut-java which create projects with all the docker configuration, it is easy to apply a CI/CD pipe, but if the project requires more scripting and configuration it gonna be a pretty hard job.

Three days of Ionic, React Native and Flutter

FabianBG — Thu, 27 Feb 2020 22:01:05 +0000

Intro

As developers, We always have the difficult desition to find the right tool to fit customer expectations, in mobile development actually exist a lot of ways to achieve the desired results but wich one you have to use, if you go to internet you found a lot of articles about wich is better and an endless fight for the best one and defining it as the silver bullet framework, but as always the best way to be sure of the pros of any technology is better to give a try. That is what I decided to do a little experiment on this 3 frameworks to understand better each one.
This article is not about wich one is better is about to identify the best qualities of each one and in wich cases are better.

Project definition

As a simple test I defined a simple application with a native integration to the camera, so the project is composed of four views, a native integration to read a qr code, JSON API service consumption and a view wich renders a long list of items.

Views

Item list: The main view wich one get data from a custom service and show 10 or the full list with a toggle button to show all or just 10.
Item form: a very simple form to insert a new item, wich redirects to item list and shows a modal with the id of a new item.
Item detail: A detail view of the item wich one consumes a get one service.
QR scaner: An integration with the device camera to read a qr code with an item id, after it succedd it redirect to item detaill view.

Day one - React Native

I decided to start with react native in wich one I have more experience, to develop for react native you should know javascript and for keeping things simple this sample app do not use the full react native stuff, like no redux no sagas just simple react.

Development

To star a new project refer to the official page wich has all the requirements. (react native page)[https://facebook.github.io/react-native/docs/getting-started]

I wanted to use type script so for the initialization of the project with ts support:

react-native init AwesomeTSProject --template react-native-template-typescript

And to run the project directly on an android device to start the development:

react-native run android

React native supports hot reloading and remote debug just shake the phone and see how the magic happen.

In this project I used these libraries:

React navigation to move between views for the installation I used the next commands:

npm install @react-navigation/native @react-navigation/stack

npm install react-native-reanimated react-native-gesture-handler react-native-screens react-native-safe-area-context @react-native-community/masked-view

For the complete guide of installation and device specific configurations refer to the official page. [https://reactnavigation.org/docs/en/getting-started.html]

QR code scanner library to use the device camera and scan qr codes, for the installation I used the next commands:
npm install react-native-camera --save

npm install react-native-qrcode-scanner --save

For more documentation refer to this page [https://github.com/moaazsidat/react-native-qrcode-scanner]

Code repo

The full code of the sample can be founded in this repo:
[https://github.com/FabianBG/three-days-with-ionic-reactNative-flutter/tree/master/simpleQR_reactNative]

App

Day two - Ionic

The second day of work is for Ionic; I had previous experiences on Ionic with angular, but I realized Ionic has changed a lot as angular changed too, they added new native integration engine named capacitor and a bunch of things, so for the Ionic development is the same javascript requirement of knowledge. As the react native app the same applies, a very simple app with the basic libraries.

Development

To install ionic and start a new project refer to the official documentation in their web page (ionic page)[https://ionicframework.com/docs/angular/your-first-app]

Ionic is not just a mobile framework it work as a multiplatform this is important because for the mobile support it is necessary to use native integration engine, in this case I am going to use the new one.

To configure or to add a mobile platform do the next config:

ionic build

npx cap add android

And finally you can develop the project in the web browser if you don't have any native component usage with:

ionic serve

And if you want to install the app on a device like an android

ionic capacitor run android

For the qr reader I used bar code scanner wich can scan qr codes too, for to install it:

ionic cordova plugin add phonegap-plugin-barcodescanner

npm install @ionic-native/barcode-scanner

This plugin has compatibility with capacitor, so it can run with the new engine.

For ionic the routing library is already included, in this case angular router, you can choose form vue and react to start an ionic project. We can use the client ionic to create pages, components and services fore more info refer to [https://ionicframework.com/docs/cli/commands/generate]

Code repo

The full code repo of this sample is on this url [https://github.com/FabianBG/three-days-with-ionic-reactNative-flutter/tree/master/simpleQR_ionic]

App

Day three - Flutter

And finally for the last day the new boy in the neightboir, I don't know anything about dart of flutter so in this project I am going to keep very simple and just the necesary not complex architectures.

Development

To create a new project I refered to the oficial page (flutter page)[https://flutter.dev/docs/get-started/install]
Install all languaje support of dart before start coding an maybe some dart quickstart.

To star the project on a device use this command:

flutter run

Development

For this development we have to include the http libray an injectable just to keep things clean.
To add dependencies to a flutter project add the library to the pubspec.yaml

dependencies:
  flutter:
    sdk: flutter
  cupertino_icons: ^0.1.2
  http: any
  provider: ^4.0.2
  injectable: ^0.1.0
  get_it: ^3.1.0
  qrscan: ^0.2.17

dev_dependencies:
  flutter_test:
    sdk: flutter
  build_runner:
  injectable_generator: ^0.1.0

Then execute:

flutter pub get

An for the qr scaner I installed a plugin fore more info refer to it page [https://pub.dev/packages/qrscan]

Code repo

The full code repo of this sample is on this url
[https://github.com/FabianBG/three-days-with-ionic-reactNative-flutter/tree/master/simple_qr_flutter]

App

Results

At the end of these three days I am writing this article, I enjoyed the app development on the diferent ways, and all the three frameworks has it own strongest points and use cases.

Development

In the development all start with the installation where all of them have a lot of information about it and not so hard, the hardest part is to configure the android or ios environment after that it is very simple. The create a new project part could be a bit different for each one but everyone has it own client and project generator.

So how hard is to develop in the react native project, all the basic app it took me about an average of 5 hours, I faced some issues with the navigation router installation and in the design of the app, I have to admit, I am not a very good designer. React has his own component for the visuals so not working with html and css can be a hard part, but react native has a lot of third party design frameworks wich provides a bunch of well designed components.

On the Ionic project the full app took me like an average of 4 hours in total more simple than react native and flutter (maybe because I know more JavaScript than dart) the designs are simpler because Ionic has a set of prebuilt components and is easy to design over html and css. The hardest part is the integration with capacitor because is new and has it complications, if you are usisng cordova maybe the same it has it owns complications.

At the end flutter was interesting to learn, dart and the way the flutter development flow was an fascinating way to create an app, the design it is a kind of different no html and css neither JSX just code, but if you like to design with code flutter is your framework. At the end It took me like an average of 7 hours, but I someway it was a new languaje for me. Flutter in the library import gave me an easy time and in the android integration too.

All of them support hot reloading on a real device or emulator and a good console log for print some debug stuff. The JSON API consumption was easy in react and ionic but in dart a kind of frustrating the json mapping to dart objects.

Performance

To measure the performace I used the Android Studio profiler tool, it provides a bunch of very interesting metrics. For all the testing I used a Xiaomi mi9 lite.

First of all, each framework has it own ways to improve the performace with a little twerks and stuff but requires a lot of fine tuning and at the end every one of them can perform better but it is not like the performance is going to incease substantially.

The first impression to me to ses how well performant is the app is the launching time, the time the app took to be ready to use, so flutter is the quicker one, then is react and at the end is ionic with the slowest start up.

For each app I get a full test cicle, wich is:

Open the app
Show all items of the list
Scroll and tap to the detail view
Go to new view and add a new item
Go to scan view and scan a qr code

React native results

CPU

Memory

Energy

Ionic Results

CPU

Memory

Energy

Flutter results

CPU

Memory

Energy

Conclusions

At the end the three frameworks offer what they promised a hybrid mobile development with easy integration to both main mobile platforms with an unified codebase. All of them has a decent performance on this simple app, and the development was a kind of easy but if you don't know dart it is going to be a slow start.

At the memory level flutter like everybody says, has the best performance, followed by react native and at the end ionic.

At cpu usage react has the biggest usage, of cpu maybe for the native render and ionic because all of the render was by the web view, and flutter very good perform ae at cpu level even if has to use native components.

The energy usage for ionic is the lowest wich means than the web view render consumes less battery than a native rendering.

I feel like flutter has a little bit of slow performance on the JSON API requests, maybe the mapping of json to dart objects or the fast view rendering of flutter is quicker than the request response.

At the development level the ionic way of develop a mobile app is like you are developing a web app and I think it is a kind of wrong, because the behavior of a mobile app it is different of a web app. So in React Native and flutter the architecture of state management out of the box is more helpful.

So which is the best? All of them has their own strengths and in my opinion and based on my past experiences these are my final thoughts:

Ionic: Very easy and flexible framework for small and a kind of informative apps, when you don't have many resources to do a specialised mobile development and need to create a mobile app with an existing web app as main concept. So you can easily get you mobile app reusing the web elements. And the final mobile app is just a helpful tool for you business.
React Native: Scales in complexity over Ionic, it requires a bit more effort than Ionic because it handles other concepts, if you are a react web developer it is easier to jump to react native, but the main difference is the component design it different form the traditional html and css it tries to keep the css attributes and html tags but wit native components so the design change and it took a bit of more effort, but with a better performance and recommended for applications with more responsibilities than can be the core of the business. It requires more resources and efforts for a team to develop an app but with more better user experience at the end.
Flutter: The new one who cames with a lot of advantages and improvements, as the case of react native you can use this for an app with can be the core business, but keep in mind the dart learning curve and the small community, flutter is pretty new but with a very high potential. I specially recommend dart for starter projects than are going to grow to be complete mobile apps, and for resources it requires more than the other two because flutter requires a kind of more time due to the new things and changing ecosystem than surround it framework.

Thanks for reach down there, sorry about the malformed redaction not an native speaker and I hope you enjoyed this article. :D

DEV Community: FabianBG

The DDD microservice with GO

Intro

Tech Stack

Architecture

Project

Tech your computer to play chrome dino game

Intro

The project

Usage

MIJO chatbot store site manager FINAL PART AND SUBMIT

Previous Post

MIJO chatbot store site manager PART 2

FabianBG ・ Apr 21 ・ 2 min read

What I built

Inspiration

What MIJO does

Category Submission:

Demo Link

Showcase

Link to Code

How I built it (what's the stack? did I run into issues or discover something new along the way?)

Next steps

MIJO chatbot store site manager PART 2

Previous Post

MIJO chatbot store site manager PART 1

FabianBG ・ Apr 19 ・ 2 min read

Goals

Progress

Gatsby theme

Twilio Integration

Next steps

MIJO chatbot store site manager PART 1

Intro

What MIJO gonna do

Tech Stack

Goals

Progress

Next step

Add the CI to your project with Azure DevOps

DevOps

PROJECT DESCRIPTION

Let's do it

Import a repo

Create the pipe

Service Connections

Pipe automatic trigger

Conclusion

Three days of Ionic, React Native and Flutter

Intro

Project definition

Views

Day one - React Native

Development

Code repo

App

Day two - Ionic

Development

Code repo

App

Day three - Flutter

Development

Development

Code repo

App

Results

Development

Performance

React native results

CPU

Memory

Energy

Ionic Results

CPU

Memory

Energy

Flutter results

CPU

Memory

Energy