Slide 1

Slide 1 text

Presto A Mobile App Maker Built with PureScript Lessons building,.

Slide 2

Slide 2 text

● Built large scale systems at Juspay, Amazon, Trilogy serving millions of users ● A convert to PureScript from Clojure / JavaScript ● Passionate about building Creation tools Hello! I’m Vimal Kumar, CEO of Juspay

Slide 3

Slide 3 text

Why do serious Apps take months to develop and millions of $$ to maintain PROBLEM Incidental Complexity is killing productivity!

Slide 4

Slide 4 text

Why are Apps Hard? Event Driven Programming model complicates transactional apps ● No clarity of flow of control - too many jumps ● UX Flows are not composable

Slide 5

Slide 5 text

Why are Apps hard? Frameworks focus on Getting started quick; Not on fundamentals to Control complexity ● Complexity of serious apps is exponentially increasing. ● Need a strong theory like Functional Programming / Category theory with extreme focus on composition. ● Hard theories need years of investment to get practical advantage.

Slide 6

Slide 6 text

Why are Apps hard? Fragmented Architecture, Need Unification ● Frontend, Backend, Persistence, External service integration, Analytics, Business Logic, Infrastructure. ● All are handled in different ways. They can be unified with a few simple building blocks.

Slide 7

Slide 7 text

We Need to remove the Incidental Complexity and enable Freshers/PMs build apps with 10x less time and effort It shouldn’t be this way!

Slide 8

Slide 8 text

How? ● PureScript - Pure FP & Types ● Free-Monadic DSL ○ UX as Conversations ○ Business Flows as Goal Trees ○ PureScript Aff continuation monad ● Unify. UI | Flows | Data - Only 3 Blocks

Slide 9

Slide 9 text

DSL - as UX Conversations User System App Welcome Tell Ask Ask-Options Ask-Search Ask-Confirm Thank Delight Suggest Cross Sell Notify Fetch Detect Search Commit Track SetTimer Etc.. App The App Weaves a. Conversation between User & System towards a Goal Goal

Slide 10

Slide 10 text

DSL - Composable Goal Trees ● Composable Goals! ● Understandable to non-tech - Designers, Product Managers Introduce Verify Mobile Create VPA Goal: BHIM Onboarding UI: Step 1 Help UI: Step 2 Help UI: Success OR Verify Mobile With OTP Verify Mobile Sending SMS API: Trigger OTP Poll SMS Inbox for OTP More steps Tree extends here… Local API: Send SMS Code Poll Server for SMS Code UI: Success More steps Tree extends here… More steps Tree extends here… UI: Welcome UI: Ask Mobile

Slide 11

Slide 11 text

Welcome Dilip to the app Ask to pay the DTH bill (why not give some incentive!) > Ask to choose DTH Operator. If a lot, let him search > Ask for his Customer ID. Show HELP on where to find the Customer ID > Fetch his Customer Name and latest due bill amount :: LOAD > Show the bill details and Ask to pay SubFlow Collect_UPI_MPIN Commit the payment and Show confirmation status. Cross Sell Ask if he’d like to set up Auto-deduct OR Payment reminder for future bills > Thank Dilip. DSL - Readable as a Narrative

Slide 12

Slide 12 text

DSL Code - Example 1 dthAppFlow :: User -> Flow Unit dthAppFlow user = showUI $ Info.Welcome user >>= fetch Api.DTHOperators >>= showUI List.DTHOperator >>= untilSuccessful $ showUI Form.CustomerId >>= fetch CustomerName >>= fetch Api.LastBill >>= showUI Info.BillDetails >>= captureUpiPinFlow >>= commit Api.UpiTransaction >>= showUI $ CrossSell.PaymentOptions [AutoDeduct, PaymentReminder] >>= autoDeductFlow <|> reminderFlow >>= showUI Info.ThankYou

Slide 13

Slide 13 text

DSL Code - Example 2

Slide 14

Slide 14 text

PureScript - Pure FP ● Composition, State Management, Conciseness and Clarity ● CPS (Continuation passing style) for the DSL Goal Trees ● Choice of PureScript - Best of Haskell and JavaScript. ● Category Theory - Functors / Monads / Applicatives

Slide 15

Slide 15 text

Just 3 Building Blocks - Unify ● UI Structure - Visual Components like React ● Goal Tree - Flows as Pure Functions ○ Represents the entire business logic ○ Unified Backend and Frontend ● Data as Types ○ Single set of types for Frontend, Backend, UI, Storage ○ Types mapped to DB data model

Slide 16

Slide 16 text

Why PureScript and CPS? LANGUAGE OPTIONS ARCHITECTURE OPTIONS PureScript GhcJS ClojureScript Haskell Like + Strong FP - Focus on Purity, Composition, Conciseness. + Types - Few errors, Easy refactoring JS Integration + Solid and easy JS FFI + JS Code Small & Reliable - New and evolving + Implements all Haskell’s features and access to most Haskell Libraries. - Large size JS and not so reliable runtime + Is a Lisp! + Strong Developer community + Proven runtime - Lacks Types - Lacks strong math / category theory foundation of Haskell CPS (Continuation Passing) Elm Architecture / Redux Pure FRP Maps directly to UX flows / flows as conversion funnel. Global state complicates transactional flows vs CPS manages local state in stack More general than CPS but complicates UX flows. Presto will add FRP support in future

Slide 17

Slide 17 text

Challenges - Steep Learning Curve Mitigation - Fast track Training to build confidence - Zero till Monads in 1 hour! - Simple DSL - Get started making apps without deep FP knowledge. - Systematic learning track for FP techniques (Juspay University)

Slide 18

Slide 18 text

Challenges - Types - Type errors: Type errors can be hard to debug sometime taking several hours of developer time. - Decrease Spontaneity: Too much focus on correctness during the process of creation & necessity to pre-think the big picture, can be a hurdle while trying to create spontaneously. Mitigation - Forcing explicit type annotations during declarations make type errors easy to debug. - A month of training developers, improve their debugging skills and spontaneity. - Move to FreeM DSL hides the scary types from general users

Slide 19

Slide 19 text

Big Benefits - We estimate 10x ● Big Change in Dev Culture! It has kindled a burning desire among devs to write concise, composable, reusable code. Scale a fresher team without need for traditional Architects. There is a big reduction in stackoverflow usage! ● Purity, Types, Composability, FreeM DSL ○ Dev Speed - Unification/Reuse have drastically improved development speed. ○ Reliability - Almost Nil bugs with Types ○ Refactoring - High confidence to try new ideas ○ Enabling PMs - Concise DSL code has enabled PMs to review code or write pseudocode. ● PureScript - JS Interop, Small Compiled JS - small app size

Slide 20

Slide 20 text

Apps in Production UPI SDK for top Apps Juspay Safe Potential for 100M+ users Other Apps: - Juspay Fuel: UPI for Petroleum - BHIM’s new features - Diksha: Teacher edu. Govt. App - Various internal ops tools@Juspay

Slide 21

Slide 21 text

Next Steps School of Functional Programming

Slide 22

Slide 22 text

Presto - Roadmap ● Visual Programming - Sketch Plugin, Flow editor, Type editor ● 1-Week Apps | 1-Day mini-apps ● Auto API Type Creator & Quick Check ● ORM + API - ~GraphQL ● Custom Type Errors in PureScript compiler ● Web IDE and Remote Collaboration tools ● Tools to Semi-Automate JS to PS migration

Slide 23

Slide 23 text

Presto Roadmap - Reactive system What if entire systems (clients, servers, storage, apis etc) are abstracted out as a Reactive system that is composed of functions! CHAT History Format Screen User1 Input User2 Input Formatted Screen Output User Id

Slide 24

Slide 24 text

Thank you [email protected] If you are interested in contributing, please contact us