I'm using React-Native. I have a mobile app and in near future I'll copy-paste it for many customers. All features will be same except colour, logo and etc. Let's assume that I have 100 mobile Apps and when there are some bugs or errors on my api or another part. I want to fix them just one time and apply it to all my mobile apps without update them on iOS-google play market. Otherwise I have to fix all my Apps separately and it will take my lot so time. I found something about it named as EXPO-OTA(Over-to-air) but that's not sufficient for me. That has some limit to update something. Is there any way to do it? Or Is it possible?
You can use react-native-config for managing each app config. like color and other configurations.
Also keep the logo in android assets and link them in js code .
After that you can use react-natve-code-push to update the js bundle over the air. This way you can sync the same codebase in every app.
Related
We have a single project that is used by 2 different clients.
The Apple store won't let us use the same icon for both, so we need to build version A with Icon set A, and then the same code as version B but with Icon B.
Do you see any way to automate switching the icons?
Note: For you to be able to upload your application on the App store it is mandatory that the App name and the Bundle id(package name) of these applications are different.
Now there is a catch Apple might or might not reject your app if it has the same resources as another. (They can be confusing at times).
I would suggest you do not take a risk change the icons, and you will have to change the app related things in any case.
Do you see any way to automate switching the icons?
I don't think there is an automated way but there is a faster way, make a list of the images that you need to change with the sizes and name of that images as per your resource files, Once you are ready with all the images directly replace them in the resources by pasting them over the existing ones and replacing them.
Once you are done with that clean build your app and your resources are freshly changed and ready to rumble.
Goodluck!
Revert in case of queries.
I have a few problems with understanding of android tv development. First of all when i had launched android tv project and was trying to create custom interface for new activity, unfortunately i couldn't find any xml elements which could help me. From the example i got some ideas that whole interface provided by android SDK collected in many fragments. I just can modify colors, fonts, fonts size, transparency maybe animation and etc. But if i really need to customize structure of controls and WTF i wanna output "Hello World" inside label!!! Is it possible? I read all articles from this link https://developer.android.com/training/tv/index.html but it is still useless for me (maybe I am unique :) ). After this suffering with google guide, i have done a conclusion that the platform so new and there is no way to do some thing except only way that was provided by google. Am i right? If not, what should i do to find successful way?
The fragments provided by Google as part of the "leanback" framework are templates designed to make it easy for content providers to start publishing to Android TV without having to worry about the technical details of building a TV UI. The idea is that a content provider can create a channel just by feeding in their video content. This ease of use comes at a cost, customization is difficult or impossible with these templates.
However there is nothing preventing you from creating your own Activities and Fragments from scratch and implementing a completely custom UI for the TV, it works just like any other Android device. Add "android.intent.category.LEANBACK_LAUNCHER" to your manifest and see for yourself.
I am styling a project built on Meteor and using LESS. I use Brackets for styling because its Live Preview feature makes working with CSS a lot quicker and more pleasurable, but by Meteor's nature it doesn't seem possible to use this feature.
Every little change I make on the code has to be detected by Meteor, who will in turn refresh the project on the browser for me, and this process is now taking anything between 5 and 10 seconds, which is entirely too much.
Does anyone know if it's possible to work on "live" CSS/LESS, using Brackets, in a Meteor project, without having to wait for Meteor to notice my changes and take its sweet time to refresh the whole thing for me?
Or at the very least least if there's anything I can do to shorten the time Meteor takes to update?
I don't think it is possible unless the developers of Brackets go an extra mile and implement a specific support tailored for Meteor.
Brackets works on top of raw CSS and HTML files and uses Chrome Dev Tools API to manipulate the page.
Meteor doesn't send raw files to the client. HTML templates in Meteor get compiled to JS DSL and CSS is concatenated and sent in a manipulated form, too.
Bracket's live preview feature would work only with quick page layout prototyping and will not play well with any modern front-end tool chain that involves compiling pages and stylesheets or preprocessing.
I want to build a mobile website for an already existing Wordpress site. I prefer to redirect the users to the mobile site automatically if the user is browsing from a mobile device. I will also need to change the contents of the pages regularly and may have to add more pages over time. But I do not want to create two different copies of the same page for desktop and mobile.
Please suggest the best option to go forward with this situation.
Thanks.
I think you would pretty much have to design your theme to dynamically change what it's doing as needed. This might just be a matter of activating the right style sheets or it might be more complicated.
There's a good book on this subject you might want to check out.
http://www.amazon.com/Professional-Development-WordPress-Programmer-ebook/dp/B004T6RKT0/ref=dp_kinw_strp_1?ie=UTF8&m=AG56TWVU5XWC2
You want two sites with the same content, but you don't want to enter the content twice, and for some reason you don't want the site to be responsive. That makes things difficult.
Theoretically you could have both sites taking their information from the same database but in reality it just makes so much more sense to build a responsive site.
In any case, if you must have two sites, you can start by detecting mobile devices with this PHP class.
I am building a website both mobile and pc version.But I am in a fix what should be used to do it.I have some question for which I am confused :
1. make a website with separate mobile version and pc version and render page depending on the device users use ?
2. Another is a single version website that would be all device compatible.this can adapt the layout according to the device resolution ?
3. if I do the thing I mentioned at point 1 , Can I built a site with wordpress and mobile version with jquery mobile ?
4. If I use a mobile compatible wordpress template I mentioned in point 2, can I use all other plugin form outside?
Please Help me.Thanks in advance.
So what should I do? building two different version ?? if yes, Can I
use the wordpress for both? do you know any plugin or way to make both
pc and mobile version in wordpress ?
This is what I did to achieve what you are aiming for:
Install WordPress as normal.
Add the Mobile Smart plugin - or possibly mobile smart pro.
Create a theme for regular desktop browsers and activate it in WordPress
Create a completely separate theme for mobile browsers. You may wish to use the sample code supplied with the plugin; I created my own from scratch.
Change the settings of Mobile Smart so that it knows which is your mobile theme
Add content and enjoy!
Please read the documentation with Mobile Smart. It is important to understand what it is doing.
Also, remember that your two themes are completely separate, in completely separate directories, so you can use completely different functions.php, headers, footers, scripts, etc. as necessary.
Quote from https://github.com/ChristianPeters/crispy-mobile that I agree with:
CSS media queries are nice. But not for mobile.
They just add up code you send to your clients instead of reducing it for mobile devices.
Imagine you want to make a responsive product page.
Do you really want to deliver a big 90KB product photo, if a 15KB photo would already fill the mobile screen?
Do you really want to compute personalized product recommendations if they are just hidden afterwards?
Do you really want mobile devices to download and interpret your whole stylesheet if half of the interface elements are going to be hidden anyway?
You don't.
If you start mobile-first, don't let your mobile performance be affected by additional desktop features.
Be kind, serve the clients exactly what they need.
If the mobile internet was fast enough and limits weren't as low as they are, I would probably think the other way. But we have to wait few years for that. For now in my opinion it is better to build seperate mobile website. But it is also very useful to have responsive design - that can't hurt even with separate mobile design.
I'm going to avoid too much subjectivity here, as everyone will have a different opinion.
Yes, I have this approach working well on my company website (www.achaleon.com). I was involved in the beta testing for a WordPress plugin called Mobile Smart Pro. It implements elements from a bigger open source project to detect mobile devices and apply a completely different theme to the mobile site. It has the advantage that you can create two completely separate themes and optimise every aspect of them for the device and the context in which it is being used. You can even serve up different content if you wish in the two versions.
This approach requires careful planning and thorough testing. It is also more demanding for the designer. I have friends in the WP community who have built sites this way. My understanding is that this requires stronger programming skills (you need to plan far more carefully than with a standard 'static' css implementation). They used cssgrid.net as a start point