This Cookbook contains recipes that demonstrate how to solve common problems while using WOLMO in you daily development. Each recipe must be self-contained in a package and will be used as a reference to help you build up an application with WOLMO.
The Cookbook will also be used as a playground to test new stuff out. That does not mean it will be messy, the kitchen must be kept clean.
- Mercado Pago: Example of Mercado Pago connection.
- Firebase Analytics: Example of Firebase Analytics usage.
- Coroutines: Basic coroutines features examples and retrofit Coroutine vs. Callback example.
- Google login: Using Google's API to verify user authentication.
- Facebook login: Using Facebook's API to verify user authentication.
- Instagram login: Using Instagram's API to verify user authentication.
- Twitter login: Using Twitter's API to verify user authentication.
- Room DB: Saving, editing and removing data from a database without a back-end connection.
- MP Chart: Creating different charts using this library. Bar, line and pie charts are some of the examples included.
- Navigation Architecture Component: A different way of navigating through Activities and Fragments.
- Data Sync Recipe: Implementation of observer that react to network request to fill information on screen.
- Tests:Testing different situation that could happened when dealing with a login.
- Koin: An alternative of Dagger to inject dependencies.
- Notifications: Implementation of local notifications with different designs (expandable text, picture, actions, etc).
- Graph QL: A GET example using this network component.
- Login with fingerprint: A simple implementation of Android Biometrics.
- Lottie: Implementation of Lottie library to import animations.
- Google Maps: Implementation of Google Maps with clustering and current location.
- Animated EditText: Implementation and example of how to do an animated EditText.
- Bounce Effect: Implementation and example of how to make bounce effect animations in adapters.
- Setup the production keystore credentials: run
scripts/keystore.shfrom the project root directory or create app/keystore.gradle file manually:
ext.release_keystore=file('...')
ext.key_alias='...'
ext.key_password='...'
ext.store_password='...'
ext.mercadopago_public_key='"YOUR_PUBLIC_KEY"'
ext.mercadopago_public_key_sandbox='"YOUR_SANDBOX_PUBLIC_KEY"'
-
Since this project contains a Firebase Analytics recipe it's mandatory to configure it. You can do it following these instructions.
-
In case you want to use Mercado Pago recipe, add your credentials on
keystore.gradle.
On the other hand, assets for project will be located in raw folder and warp.py script will create all drawable needed for all resolutions. For more information, you can check it's repository: https://github.com/Wolox/warp
- Fork it
- Create your feature branch (
git checkout -b my-new-feature) - Commit your changes (
git commit -am 'Add some feature') - Push your branch (
git push origin my-new-feature) - Create a new Pull Request
This project was created by Emanuel Lamela and it is written and maintained by Wolox.
WOLMO Cookbook is available under the MIT license.
Copyright (c) Wolox S.A
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.