Skip to content

Latest commit

 

History

History
77 lines (59 loc) · 2.37 KB

QR-generator-test.md

File metadata and controls

77 lines (59 loc) · 2.37 KB
Raw

QR-generator

Make sure you have read the README.md first.

Be sure to read all of this document carefully, and follow the guidelines within.

Context

  • A client needs to display a QR code in their App.
  • The QR code can be used to identify one's profile or a certain feature.

Requirements

Tasks

  1. Build a simple API server that provides an endpoint which generates a random seed used to create QR code. (if you cannot build an API server, we can supply a lambda to do this for you)
  2. Build a simple App that can call the seed endpoint and generate a QR code based on the seed.
  3. Build a "Scan" feature that can demonstrate how it works (see the mock) and how it could be validated with another endpoint.
  4. Be sure the app will use the below UI and will have a navigation patterb present.
  5. Write clear documentation on how it's designed and how to execute the code.
  6. Provide proper unit tests.
  7. Write concise and clear commit messages.

UI

Here's a quick mock-up of how it could look like (simple like Material Design!): UI Example

API

(in Open API 3.0 format)

paths:
  /seed:
    get:
      description: Get a seed that can be used to generate a QR code
      responses:
        '200':
          description: seed generated
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Seed'
components:
  schemas:
    Seed:
      type: object
      properties:
        seed:
          type: string
          example: d43397d129c3de9e4b6c3974c1c16d1f
        expires_at:
          type: dateTime
          description: ISO date-time
          example: '1979-11-12T13:10:42.24Z'

Tech stack

  • API
    • Use anything for the backend. We generally use Node.js, so this is prefered but not required.
  • Cross platform
    • Use Flutter
  • Android
    • Use Kotlin
  • iOS
    • Use Swift

Advanced requirements

These may be used for additional challenges. You can freely skip these if you are not asked to do them; feel free to try them out if you're up for it.

  • Provide an auto-refresh strategy, for example with the expires_at value.
  • (Android) Use DI with Dagger2
  • Provide an offline QR code access strategy, for example with a cache.