Forem: moagggi

DO backed static random number generator

moagggi — Sun, 10 Jan 2021 14:18:30 +0000

What I built

I built an Random Number Generator for the purpose of getting known to DO App Platform.

Category Submission:

Random Roulette

App Link

https://dt-do-app-platform-hackathon-evut5.ondigitalocean.app/

Screenshots

Description

The UI is pretty basic but it fulfills the needs.
It looks and works like a RNG, so it must be a RNG!
Hopefully the UI is wacky enough for the submission category!

Link to Source Code

moagggi / dt_do_app__platform_hackathon

dt_do_app__platform_hackathon

A random number generator as a submission to the DigitalOcean App Platform on DEV.to

Read the full submission under: https://dev.to/devteam/announcing-the-digitalocean-app-platform-hackathon-on-dev-2i1k

View on GitHub

Permissive License

MIT

Background

I've already published other RNG apps to get known to new techniques and actually had a successful extended RNG.
It's just super easy to get some basic knowledge about a new language/stack by replicating something you already know.

How I built it

The RNG itself is a simple descriptive html page with inline javascript. This makes it perfectly fitted for the "static site" deployment through DO App Platform.
Though I didn't know about DO's App Platform before, the process from first commit to deployment is pretty straightforward and easy. It took me under 5 minutes to get DO up and running! Sweet :)

Additional Resources/Info

Although the result will never be best-of-class, such a simple project always encourages me to learn new things - in an easy way. Once you've digged deep enough into a new thematic, you're always free to "come back" and improve the initial try.

If you never start, you never level up!

Web Monetization API Wrapper for Android WebView

moagggi — Thu, 21 May 2020 23:26:07 +0000

What I built

I built a Web Monetization API events wrapper JavascriptInterface for Android WebView using Java.
The usage and logic is quite the same as with the JavaScript API, as the events are actually the same. :)

Getting the events wrapped on the Java side in the end is as easy as follows:

WebMonetizationWrapper wrapper = WebMonetizationWrapper.createAndAddInterface(webview);
wrapper.addPendingEventHandler(/*your Handler*/);
wrapper.addStartEventHandler(/*your Handler*/);
wrapper.addStopEventHandler(/*your Handler*/);
wrapper.addProgressEventHandler(/*your Handler*/);

Submission Category:

Foundational Technology

Link to Code

moagggi / AndroidWebMonetizationWrapper

A WebMonetization API Wrapper for Android

AndroidWebMonetizationWrapper

A WebMonetization API Wrapper for Android

Prerequisites

Any Android IDE
GSON Dependency com.google.code.gson:gson:__current_version__

Usage

WebView webview = new WebView(context);
webview.getSettings().setJavaScriptEnabled(true);

WebMonetizationWrapper wrapper = WebMonetizationWrapper.createAndAddInterface(webview);
wrapper.addPendingEventHandler(/*your Handler*/);
wrapper.addStartEventHandler(/*your Handler*/);
wrapper.addStopEventHandler(/*your Handler*/);
wrapper.addProgressEventHandler(/*your Handler*/);

webview.setWebViewClient(new WebViewClient() {
    @Override
    public void onPageFinished(WebView view, String url) {
        super.onPageFinished(view, url);
        //attach after every page load
        wrapper.attach(view);
    }
});

Additional

See https://webmonetization.org/docs/api for more information.

View on GitHub

Demo

I built a small demo app around the wrapper, for testing, with a TextView, Button and a WebView (the white area with 5 buttons).
As the demo app just mimics/polyfills the embed Web Monetization browser/extension logic the demo app has to be manually initialized and attached via two button clicks (init, attach).

IRL no polyfill is needed, as the API is then already populated (or absent) from the start.

After initialization and attaching, the API events are the same as you wouldn't get from any other guy (c). I mean, legit Web Monetization API.

There is the stopped alas pre-pending state

as well as the then following pending state with event data

The data ATM is the same (despite the event name) for pending, started

and stopped

Then there's also the progress event between with the current fragment and the total (that's the manual sum of all previous fragments)

How I built it

I basically started with noting the event names and data as well as creating the needed String constants and separate Java sub- and super-classes.

After that I created the Java side Handler register and invoke logic.

Finally I've written the JavaScript code registering all events, that's wrapping them and passing it through to the Java side.

It is important to re-attach the wrapper after each page load, something fast accomplished with the next lines

webview.setWebViewClient(new WebViewClient() {
    @Override
    public void onPageFinished(WebView view, String url) {
        super.onPageFinished(view, url);
        //attach after every page load
        wrapper.attach(view);
    }
});

Now you're having the Web Monetization events fully in your Android app.

Additional Resources/Info

See https://webmonetization.org/docs/api#browser-events for more.

Starting working on my new Hackathon project

moagggi — Tue, 12 May 2020 23:02:35 +0000

I'm excited that I am starting on building a Java Wrapper (for Android) for the inbuilt WebView creating a JavaScriptInterface that's able to expose the JavaScript API to Java.

The repo on GitHub is already live and I start creating the code.

moagggi / AndroidWebMonetizationWrapper

A WebMonetization API Wrapper for Android

Stay tuned and good luck on your submissons, too!

Integrating Finnhub.io with Twilio

moagggi — Thu, 30 Apr 2020 20:33:31 +0000

What I built

I built a Integration for Twilio to get the current stocks quote from my favourite api Provider.

As there was no app using the already published api from Finnhub that fitted my Needs, I thought this would be the perfect fit.

Instead of making a complete app myself, I decided to use this correlation, to use a Twilio Integration. The result should work on-the-go, be easy to use, be easy to implement and most importantly, work in rural Areas without excessive mobile Network Access.

This were the reasons to use the Twilio Service with SMS capability.
The result fitted all my needs, was easy to create and even works without Internet Access. In the end using SMS for the request initiation fitted perfectly.

Category Submission:

Interesting Integrations

Link to Code

https://github.com/moagggi/twilio-dev_to

How I built it

I used the awesome prebuilt official PHP SDK from Twilio with no issues, as well as the inbuilt PHP functionality.

Additional Resources/Info

To successfully deploy the project you need a self controlled PHP environment, as well as an API-Key from Finnhub.io (get one there, it's free).