Code Monkey home page Code Monkey logo

xrcade's Introduction

This project was bootstrapped with Create React App.

Available Scripts

In the project directory, you can run:

npm start

Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.

The page will reload if you make edits.
You will also see any lint errors in the console.

npm test

Launches the test runner in the interactive watch mode.
See the section about running tests for more information.

npm run build

Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.
Your app is ready to be deployed!

See the section about deployment for more information.

npm run eject

Note: this is a one-way operation. Once you eject, you can’t go back!

If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.

You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.

Learn More

You can learn more in the Create React App documentation.

To learn React, check out the React documentation.

xrcade's People

Contributors

isnit0 avatar

Stargazers

Ben Foxall avatar

Watchers

Gordon Williams avatar James Cloos avatar  avatar

xrcade's Issues

Sharing games

The sharing should be to our listing of the game, not to the game directly

  • Facebook
  • Twitter
  • Reddit

"Hackathon" Todo list

We should split these into separate issues when we meet on Thursday morning, these are notes to remind us :)

  • Marketing stuff (SEO, marketing plan, etc)
  • Content Stuff
  • Extra features?

Personally, I'd like to be able to launch soon after we meet 😄

Basic WebVRLib

TODO: split into multiple issues:

  • Leaderboards
  • User data
  • Tips
  • Adverts?

Metrics

Numbers we should collect:

  • How many visitors?
    • User agents/devices
  • Click-throughs to individual games (useful for early stage of requesting devs to publish with us)

Name

Important things:

  • We want to appear Oculus Quest specific for now
  • Should be easy to type in VR (short and end with .com)
  • ...

Ways Forward:

  • Should we go with a quest specific brand first, then "rebrand" if it makes sense? (we could always just redirect multiple specific domains to an actual one).
  • Should we find a generic one up front?

Questions:

  • Which option is better if we want to sell to someone?
  • Does one option make it easier to grow early on?
  • What would be the down side of re-branding?

Creators/About

Thinking about it, it would be nice to be able to point other people at our public profiles.
Maybe just doing the classic "Made with ❤️ and 🍕 by @gfwilliams and @ISNIT0" type thing in the footer

Content

We will need content.
To begin with, we will manually curate the list by going through existing webvr aggregators and "awesome-list"s

I think Gordon knows the most about this for now.

Early on

We would like to allow people to submit other people's work publicly. We can then manually contact developers and suggest they repackage their game and maybe monetise with us

Eventually

We will need to encourage developers to publish exclusively on our platform. There are other tickets explaining these features.

Original thumbnails/videos are different aspect ratio

I think they may not be 500x250 after all. Chrome inspector thinks 500x281, which is a 16:9 aspect ratio :)

To be honest that extra height would make the videos a lot easier to see, so shall I just re-run my scripts and create images/videos of the new height?

Also, could we maybe just do: 512x288 - this is actually 16:9 rather than a slightly iffy approximation (and may be marginally more efficient as IIRC often H264 type stuff pads everything to the nearest 16px)

Basic directory site

  • Listing of apps
  • Rating (hard coded)
  • View video demo of the app
  • Click link through to app
  • Get permalink for app
  • Analytics
  • Sharing

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.