We have a requirement to build apps within an app, like how we have a main app called, Google and when we click the app icon, we get options like gmail, chrome ...and those apps function independently..How to organise these apps within the main app.
Could anyone give some basic idea on how to build micro-apps for iOS.
From my point of view, there is no such thing as a "micro app". What you seem to want to achieve is put various functions in one single app, what is not a good idea.
Thinking about your example with Google, they arent doing what you are mentioning. If the functionality is big enough, they put it in a seperate app (gmail, maps, ...). Same goes for you.
If you really want to go that way tho, i would highly suggest to make seperate storyboards for every "micro app" to keep things easier to maintain.
Related
I've created an app in Rails which can be put on the homescreen of an iPhone. With some javascript hacking, I can make sure all internal requests stay within that frame. While this works, there are also some drawbacks. With the rise of PWA, I was wondering whether that would be a good alternative, so my questions:
Isn't PWA overkill if my only requirement is that the app is instalable?
Do I need to install all the service workers to get the PWA installable?
Is there some alternative I might have overlooked?
To answer your questions:
From google's PWA site:
Progressive Web Apps are user experiences that have the reach of the web, and are:
Reliable - Load instantly and never show the downasaur, even in uncertain network conditions.
Fast - Respond quickly to user interactions with silky smooth animations and no janky scrolling.
Engaging - Feel like a natural app on the device, with an immersive user experience.
This new level of quality allows Progressive Web Apps to earn a place on the user's home screen.
So my answer for your first question is, no. It's not overkill, it's exactly for that (and more, but you don't have to implement all the available features).
If you want the user to feel like the user is on a native app, yes you have to. There are a lot of basic service workers and builder to use that enable basic caching already.
Here is a checklist from google on what you need to have a "proper" PWA.
Microsoft suggests this site to get you started for basic modern websites.
Except for using something like Cordova, I don't see any alternative for PWA's that suite your use case, the only alternative I see is leave it as it is, if you don't need a PWA. The hype is currently high and you should definitley check it out. But as always, you don't have to if your product works as it should.
I am developing a system which has both Tablet & Website.
It's a tool and now more and more professional come to register on my system.
I want to do ads on the system. Both website and Tablet(iPad for now but will support android).
I searched a lot and MoPub seems a good option. I did utilize the MoPub SDK to iOS and website. it works good except, it's for mobile only.(Said by MoPub official, I feel sad because it meet every my requirement except this one. I need do ads on website also, even on PC browser.)
I want find an alternative of MoPub, but seems there is not much options.
Is there any one who knows this and give me some suggestion?
My requirement is:
As the system admin, I can create Ads order for customer, I can define the Ads content&layout displayed on both iPad & website. I can put link on ads and the link should works on both Tablet App and PC website.
As developer who integrate the Ads platform. I can utilize the SDK to request Ads based on customer keywords I defined.
I can see a lot of reports for the revenue, daily, monthly, single ads, multiple ads.
The very basic Ads configuration
Well formed SDK on iOS and android. so that I can integrate quickly.
Thanks!!!
hey man) you’re asking and trying to compare different things: you ask about MoPub Alternative and one of your requirements is that the solution should support both Web and Mobile. MoPub is for mobile platforms (ios/android) only. Frankly speaking both web and mobile ads have own features and nuances, that’s why most of current solutions are focused either on mobile or web. Not sure I can provide lots of info about platforms for web, but this article might be useful for you https://www.adpushup.com/blog/the-best-ad-networks-for-publishers-2015-edition-moving-beyond-adsense/
Mopub is a really good platform, but if you’re still thinking about alternative (i’m speaking about mobile) take a look at mediation solutions. there are lots of them: AdMob Mediation, Heyzap, Fyber, Appodeal and many others. all of them have pros and cons. if you like manual customization and settings give a try to the first three, i’ve heared lots of good things and positive reviews about HeyZap and Fyber, though im not a big fan of "handjob" =). this way you’ll just have to create accounts in networks you’d like to use in mediation. but i personally think that its slightly a longer way, at least for me, because the performance of each network depends on your app and it need to be understood. so you’ll need to analyze which ad networks perform better for you. i’m not a big fan of everyday analysis and comparisons, so i stick to programmatic services, like Appodeal for instanse. the point is that it works out of the box, automatically, without manual settings for each network and account, that helped me to save a lot of time for working on other projects. i’m pretty much sure that you won’t get a 100% right answer, because each developer has own priorities and aims. I suppose that the best way it to collect info on forums like stackoverflow, reddit, and make your own research accordin to your needs. good luck
We have a functionality that we would like to be available outside of the app and are wondering of there is a way to launch a small control that lives when the app isn't on, and can be "overlayed" onto any other app.
The control is just a way to help people with disabilities navigate the phone easier using new gestures.
Maybe something with a settings bundle?
What I think you want to look into is creating Cydia Substrate (formerly known as Mobile Substrate) tweaks.
Substrate tweaks allow you to inject code into other iOS processes, including the SpringBoard itself, Preferences.app, or any other app or framework.
In addition, you should checkout Ryan Petrich's libactivator, which allows you to build extensions that listen for different user actions or gestures, and let you respond to them.
This advice assumes you are deploying to jailbroken devices, as your question tag suggests. Without jailbreaking, you won't be able to do much useful in this area.
References
http://iphonedevwiki.net/index.php/Libactivator
http://iphonedevwiki.net/index.php/MobileSubstrate
I have two iPad apps, one which downloads data from a server and stores it on the iPad and another one (the main app) which uses the data later.
(It would make sense to combine the two but it's a client requirement)
But I see no way to share the data between the two apps.
I have heard there are ways to do it using:
Custom URL Schemes
Document Support on iPad Devices
UIPasteboard
But I cannot find any thing explaining how to use any of these effectively.
Can anyone point me in the right direction.
Just to clarify:
It is an iPad only app
Both apps will not run at the same time
Basically I need to access the documents or caches folder of one app from another
Using iCloud or any other third part service is not possible
It would be great if I could make the downloader app into a sort of configuration page for the main app (if it is even possible)
So keeping these in mind which one would be the most suitable?
This link at github may be useful... Looks like someone has already made a file manager, using these elements you may be able to do what you are looking for. But as far as I know, your app is extremely sandboxed and does not really interact with other apps/the file system very much at all (Apple is very limiting that way)
EDIT
this post seems to have the explanations of local data sharing methods you were looking for. None of the methods in this post requires any connectivity, just a device and 2 apps :) Good luck!
I have a big question about how newsstand works.
When you have to create a new magazine(issue), how do you do it?
I mean, Do I have to implement new code for each magazine (with new views and new view controllers) which doesn't look the same as the others and has interactive content? In this case, how do I add/upload/integrate them to my newsstand app which is already in the market?
In the case that It doesn't work in this way, How does it work?
Thank you very much in advance.
Your question really goes to the heart of how Apple has chosen to implement Newsstand. Basically, there are three possibilities for using Newsstand: use image/pdf content, use HTML5 content, and use the CoreText native API.
I take it from what you are saying that you would like to use the CoreText API. This is difficult to do in the Newsstand framework for the reason you suggest: you really are not supposed to upload a whole new app with each edition.
There are two possible solutions. The first is simply not to use Newsstand. Instead you can publish your magazine as an app, and simply upload a new app for each edition. This means you miss out on things such as subscriptions and the "double-listing" promotion of Newsstand, but you can make high-quality, native, custom interfaces.
The second is to do what I am in the process of doing right now, which is to develop something like an XML encoding that when loaded into your base app will generate the kind of interface you want.
At least that is my analysis so far. I would be so pleased to be told I'm wrong, really. But I do think this is one of those cases where Apple hasn't really thought through what they are offering. Maybe next year it will get better!
If you use the Baker framework you can download the interface elements (html, images) as "issues" and the code part (Baker framework) will stay the same.
To add a new issue you do the same as you do with downloading the PDFs using NKAssetDownload. If you're using Baker you will want to extract the whole "book" into the documents directory.