We are using Meteoric today. However, if I was choosing today I would probably go with React and Reapp as this should integrate more natively with Meteor 1.2 and React.
1 Like
While I’m not the biggest fan of React I agree with @skirunman React and Reapp is the best option right now.
1 Like
I will say that I think Meteoric is still viable if you want to stay with Blaze. Just be ready and willing to support the code base yourself. We do this by forking and installing as a local package.
Do you have any links to usefull recources “how to start mobile dev with meteor”? For me it is not clear how to separate(or maybe combine) code for web and mobile. Does it somthing like on meteor when you separate code for client and server in different directories client/ and server/ ? My future app should be synchronized with web and should share part of code. Now I can’t imagine how it should be.
1 Like
Yes, struggled with same thing. Right now we are focused on mobile so have not implemented separate template/view code for web. When we do, we will likely go for an all package architecture following patterns as discussed here http://meteorpatterns.com/Sewdn/project-builds and here http://meteor.redandivory.com/#/
Good luck!
1 Like
Different interface based on devices
Seems to be a workable solution at the bottom of that thread, along with a github example.
Meteor as backend/subscriptions + http://polymer-project.org version 1.0 + vulcanize tool.
The secret knowledge: Try to keep /public folder on server minimum size.
I’d go with f7 if I were you. Its very stable and has material and ios design from the same codebase.
F7 looks great, but what about intergration with Meteor and reactivity?
As I see Framework7 doesn’t use any library, just HTML+CSS. Does it mean we can choose?
Just use the F7 package for meteor, it will just work. 
Ok. I will try. Another question. I plan to reuse code for web in my app. How I should organize project to achive this goal. Now I have usual structure:
|- .meteor
|- client/
|- server/
|- public/
How to build mobile app using only mobile code not include whole project code?
Maybe like this:
|- .meteor
|- www
----|- client/
----|- server/
----|- public/
|- app
----|- F7 and mobile staff
I plan to reuse some helpers and methods and use same collection and share documents between web and mobile.
Hello again.
Finally, I decide to separate structure of web and mobile app. And now it looks like this:
workspace
|- web_app
|----| .meteor
|----| client
|--------| lib
|--------| templates
|--------| styles
|----| public
|----| server
|- mobile_app
|----| .meteor
|----| client
|--------| lib
|--------| templates
|--------| styles
|----| publict
|----| server
If I have to share some code between web and mobile I just create a symlink.
As a mobile framework I will use Framework7 + Meteor + React
1 Like
f7 in combination with meteor seems really nice!
Gonna follow this tread to see how people are gonna implement that.
I tried some and choose this
nobutakaoshiro:framework7-ios-materialLoftsteinn’s packages. As long as you use the latest f7 version (1.2.0) you should be good.
Some of you suggest to use reapp. What is that suggestion based on?
I had a quick look and I see it is hardly maintained anymore and there is no clear way (to me at least) to integrate it with Meteor.
Now the MDG will move away from Blaze, the Meteoric package will be no longer maintained. The question is, what is the alternative for building mobile apps now? I like react, no problem to use that instead of blaze, but what is the recommended css/html framework for mobile that works with it?
1 Like
Hi @achirkof, I’m curious about your progress. How is it going ? Is it good to go with F7 + Meteor + React ?
3 Likes
I’m curious about it too!
framework7 is unbelievable, just tested it with an iPad 1 just to see what i get and most of things worked.