Why do you think you need an application for this? Applications were made before mobile devices / web browsers could handle real functionality. That’s all changed now and having an app for each OS should be a secondary concern rather than a primary one. It’s perfectly fine to do both.
Doing what you ask may be made much simpler though if you add the functionality to an existing mobile friendly site instead. Then this would cover more device platforms than just those two.
XCode can’t be used for mobile platforms don’t run iOS. Even if this were not the case, ignoring platform differences between iOS and Android would frustrate users of each platform. Each app needs to implement platform specific optional guidelines to be a quality app.
Do you already have a mobile friendly / responsive site? If not, start there and only if you think you still really need it should you create separate apps. The site and and all the apps will need to be maintained separately and doing it right can be expensive. Having one site to cover it all will be much less work / expense to begin with. You can always add on later as you grow.
If you’d rather not do any of that, you might even be fine with a service like following – http://www.happytables.com
While not a requirement, this item would seem to exhibit a total disregard (not unique to your item) for the WordPress style guide and the platform itself. Your item shouldn’t look like a non native web app that was then turned into a WP plugin just to cash in the platform’s popularity. Even if that’s the only motivation (other than say – making great software), you could stand to be more subtle about it.
Perhaps if / when you redesign, consider adopting the WP Native styles, etc (as made abundantly clear if you search even just a little bit). That would be a distinguishing characteristic (way to stand out) right there since it sadly gets often overlooked.
I’m a virtual nobody on the web but here’s an article on the matter from someone who’s more well experienced and known (in WP circles anyhow). Be sure to read the comments too!
We Should Be Using The WordPress Style Guide – https://tommcfarlin.com/wordpress-style-guide/
Awesome article but definitely not for the TL;DR crowd. Lol.
Talks about way more than just Thesis. Very detailed and interesting read. I wasn’t an active WP user back then and find the history to be quite enlightening.https://poststatus.com/thesis-automattic-and-wordpress/
I do like the bit he said about clarifying the split by saying GPL PHP instead of just GPL by itself though. Even the 100% GPL items here contain items that aren’t 100% GPL which in turn means they’re not licensed properly. It’s inaccurate at best and disingenuous at worst. So, spelling things out more would be a good thing, right?
This is Matt Mullenweg’s take on the split license approach…
There is No Such Thing as a Split License – http://ma.tt/2015/07/licenses-going-dutch/
I’d be interested to hear how various Envato buyers and authors feel about WordPress items that are licensed this way?
Do you agree / disagree with Matt? Share your opinion.
+1 @ BoldBlocks.- totally agree on this.
Here’s an example of what not to do courtesy of the “CSS Hero” WP plugin. I don’t use it but have dealt with people that have / have had it installed. It uses ridiculous tactics like this. Sadly, you won’t realize what they’ve done until you’re already a customer. It’s almost like a punishment for buying it legitimately.
However, they apparently also felt the need to go above and beyond the norm to make things more difficult than even what has been described here. When you buy the product, you also likely won’t realize that you weren’t given the full product (source code) either like with most WP plugins. They purposely do not distribute the full source code but rather just a shell. It’s a client / server based plugin product. It’s not encoded or encrypted but simply incomplete.
What this means is that you’re only given what amounts to a client to connect with their server. It needs to phone home each time you invoke it’s user interface on the front end of your site. The license verification code that would otherwise be the attack vector for someone wanting to hack the system is stored remotely just out of reach which is good for them. If they’re ever down though, you don’t have internet access, the company goes out of business, etc – you’re pretty much screwed whether your license is real or not.
Wow. Regardless of whether it works or has worked before. Don’t just embed scripts like that. Read all these in their entirety. Don’t scan / skim. Read all of it.
jQuery is already part of WP core and by default is setup for no conflict mode. Adding jquery and other scripts incorrectly to a WP site will likely cause plugin / theme conflicts immediately or later for you or someone else. Just don’t do it.
The menu will never work reliably until jQuery, the menu JS and the menu CSS are all at least enqueued properly. Then the document must be in a “ready” state.
You’ll need to integrate with the WP Menu system. I’ve not built a menu walker myself but I know what they are / for. Do not just hardcode HTML into php because it’s easier. This is just how menus work in WP.
Lastly, none of this code really belongs in a theme or child theme (read – don’t put it in the functions.php). Instead, you should endeavor to put it into a plugin for maximum modularity / maintainability.
Here’s a popular way to begin a new plugin without having to start from scratch as much has already been done for you and it’s free too – http://wppb.io
So, there you have it – adapting a JS menu into WP is easy to do WRONG. Learn to do it right. Figuring out how to extend the WP walker class and the Appearance
> Menus screen is one of those things on my to do list but I keep having to put it off. Eventually I’ll get there. Never stop learning. :)
I’m interested in people’s reactions to this news. Are you in favor or against it? Do you think it will affect the future of competing eCommerce solutions for WordPress at all?
Why or why not?http://www.woothemes.com/2015/05/woothemes-joins-automattic/