@Fran-Diox If you give me the locations that should be included in the App, I could make you an Tokyo version.
I will maintain one code base for all the cities. So its really not much of a task for me, to open a new city.
My next Tasks are:
Btw since your are a part of the Onsen Team, I submitted my App for your Showcase, if interested.
I use
const devWidth = (window.innerWidth > 0 ? window.innerWidth : screen.width)
with that i can calculate the height of my items. I use it here:
Im an nightlife eventhost who loves to code. Yeah thats probably a pretty rare combination. I find it pretty difficult for ppl to find out whats going on the weekend on Facebook or similar sites, since you have to find each club individually and there is no collection. Therefore I created an app with React-Ionic, which is not maintained anymore and I also made some mistakes. So I started a new one with Onsen. And im so happy that I know have a framework that is maintained and makes it so easy to code for multiple platforms.
Im not 100% finished, since I try to speed up the initial loading time and ill probably add features all the time.
This version is for my city Frankfurt, Germany. But all that is needed are the IDs of the Club Fanpages. It gathers all the Galleries, Events, Locations etc from the API then. Optimized to reduce data loading.
If someone is interested Ill release the Code on Github, though I dont find its really that of a masterpiece. Im just proud that I eventually can release something to a showcase. It’s my first App, and I Learn Coding sidewise to my ordinary job as Marketeer and economic student
It was due a error in my componentDidMount() that tried to register a gcm messaging service. I got a notification in the safari console, didnt thought it would hinder the whole app in something. So probably a takeaway for me is to fix all console errors first 
solved. Will post solution later.
When I open my app on a Safari on Windows or in my iOS App my Meteor App with the React-OnsenUI Framework doesnt select an initial Tab.
If I open it on Chrome, Firefox or on a Safari in a Mac! It works as expected.
The demo
https://onsenui.github.io/react-onsenui-kitchensink/
tested on Safari on Windows
works too. Havent compiled it on an iOS App yet.
Im running against a wall for days with this issue since im almost using the same code as the demo
Demo Tab Code
https://github.com/OnsenUI/react-onsenui-kitchensink/blob/master/main.js
My Code
https://gist.github.com/JWPapi/2af216e6e1d696e988c07c75900fd7bb
Ok, so the gap came by the Onsen Status-bar-fill Utility Function:
https://onsen.io/v2/docs/js/util.html
As you can see there you can disable this function with
ons.disableAutoStatusBarFill().
So did I in my Meteor App, its has a own function for this.
The reason why it just appeared on the second page was that I somehow manipulated the design with my tab navigation structure. I fixed this before I found the upper solution and than had the gap on all pages lol.
Ok i fixed it, ill write how for furture readers later. I have to attend some meetings now first. But dont waste your time helping me.
I tried to remove the Back Button and I made the Toolbar:
<Toolbar>
<div className='left'></div>
<div className='center'>{this.props.event.name}</div>
<div className='right'></div>
</Toolbar>
To see if its maybe because of the missing right div that wasnt there before or the back button, but it wasnt. I cant see anything in the css too…
I now removed the toolbar completely to see if its a problem inside the toolbar but it isnt. There is a gap even without a navigation bar!
The strange thing is that it only happens if I run my meteor app with meteor run ios or build an iOS App, its not happening if I just open the URL on an iPhone.
So the Cordova inAppBrowser somehow thinks it has to gap the content. But curiously just on subpages. My Im doing something wrong with the navigator. Maybe im openinng an new navigator instance and that instance doesnt know, that it doesnt need to make an gap :/
Im really stuck right now
Yeah I know the button on the top is not correct, but that’s not what im asking currently. In the second picture is a margin between the Header of the App and the Status Bar that shouldn’t been there.