Blog.Oshi.io
The official blog for Oshi Bitcoin Casino

Oshi’s New Year’s resolutions

by oshi in Oshi Roadmap

Some important things were doing early 2016.

Immediately….

There’s been a problem with cubits taking transaction commissions from both us and you. What this means is that you deposit ‘X amount’, a slightly smaller figure appears on your deposit account. Although the numbers are really tiny, it’s an issue and it’s a huge priority to sort out as soon as possible.

Very shortly…

The site.
We had made the decision back in early December to push on with phase 2 of the site. This will be transformative and will take us in the direction we’d always want to go; e-commerce.

Why e-commerce? Because they do navigation and usability far better than most iGaming casino operators.

We have built a working early alpha phase site, which is coming along very well. If you’re interested, we have an HTML only demo site which is essentially a sophisticated wireframe to show you which way were going: http://5.10.105.45/~nine0web/oshi-2.0/index.html

2016-01-03_180818

 

The site is based on a similar user flow that you’ll find on a real estate website, or a car sales website. I.e. there are a moderate number of choices (less than 1000) with filters and sort lists to help you find the thing you want. We’ve also kept the ‘Netflix’ look, because it’s pleasant and makes the game graphics stand out.

Mobile

This is absolutely huge… And is foundation for the new website. We’ve done everything we can to make the site fully responsive all the way down to being usable on iPhone 4. Our overall plan is to make the site ‘device agnostic’, which simply means it really does not matter what device you use, the site will be fully functional for you.

By taking a really well thought out existing theme from theme Forest and reworking it for our use case, we’ve got something that from a CSS/HTML point of view is beautifully coded and pretty robust.

Theme

Un-Lasvegas… This idea percolated from the get go of Oshi. Why should a casino shout, disrupt, make themselves unwanted by being too loud? So were taking another direction which is to let the games do the talking. This idea has come from Netflix, Google play, Amazon prime video and of course our main influencer; Steam.

They all share a number of things in common;

  • the site is ‘invisible’
  • navigation is really easy
  • the content is King, or Queen 😉
  • they try to make themselves memorable by being brilliant at what they do, not by ‘shouting’ like so many casinos do.

And that’s the direction we want to take.

What’s next?
Were keeping an eye on existing live site, making sure there are no major issues and in the meantime were pushing for a beta release of Oshi 2.0 somewhere around mid January, assuming everything goes smoothly.

We’ve done a product roadmap which I’ve talked about it here in this post: http://blog.oshi.io/roadmap/general-product-strategy-70.html

In short, the stuff we thought was just daydreaming is turning into a reality.

Our immediate priority is to make it easy for you to find games that you love to play.

This is where really good categorisation and attribution of games is critical, along with a simple tagging system that makes it easy for you to find any game you with your preferred characteristics that you want.

We’ve also built the foundations for very intuitive personalisation, the kind of thing you’ll get on Google, Amazon and eBay. So when you do a search, or pull up a list of games, one of the sorting options will be ‘most relevant’ and when done properly, it’s going to make it really easy for you to find the games you most love to play.

Finally
Mike will be working with the community to get feedback on features that you want and we will be pushing out releases constantly for the next number of months.

I’ll keep you posted on roadmap developments as they come through.

Thanks

Nick

Leave a Reply

Your email address will not be published.

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

AlbanianArmenianAzerbaijaniBelarusianBulgarianChinese (Simplified)Chinese (Traditional)CroatianCzechDanishDutchEnglishEstonianFinnishFrenchGermanGreekHindiHungarianIndonesianItalianJapaneseKoreanLatvianLithuanianMacedonianNorwegianPersianPolishPortugueseRomanianRussianSerbianSlovakSlovenianSpanishSwahiliSwedishThaiTurkishUkrainianVietnamese