Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I'm just starting to develop some OSX apps, and would prefer not to pay the $99 developer fee until I have something legitimate to put out. My issue is that I'm trying to share the small apps I do have with some friends by archiving them in Xcode as unsigned applications. While I can send these via e-mail and airdrop and it works just fine, if I want to put one of them up on a site like Mediafire so that other people can download them (without me having to email everyone individually), the app gets separated into a bunch of different files for the icon, plist, etc. Is there any way I can share an unsigned app like this and just keep it so that people can download and open the app as is? (or do something like a dmg, which seems to be the route many 3rd party apps go).
Go to the finder and Zip the Application you create. This can be done easily by selecting your App and then choosing File > Compress. The ZIP file is good for downloads, but will present a warning to the user that they are using an unsigned binary.
You can use Xcode to create an Archive, go to Organizer, select the Archives tab at the top and select Distribute, Save for Enterprise or Ad-Hoc Deployment. Then you will have to choose your dev code signing identity. Click next and it will ask you where you want to save your .ipa file.
You can distribute this along with your dev provisioning profile and have your friends drag and drop the ipa and profile onto itunes to install the app.
I know this works with Ad Hoc distribution (which you probably need to pay the $99 for) but it may work with just a developer cert/provisioning profile.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
I have developed a product based mobile application which should only be available and downloadable for my consumers who are using my product.
Please help me understand how the private/restricted app store works.
Is there any way to provide a direct download link from my website?
you could maybe give a try to companies providing enterprise private app store.
With such service you can create your own company app store and host your native apps, this would maybe make your app management easier.
You'll also be able to control distribution, updates and user access. For instance, you can create groups of customers with different right access, they will receive a direct invitation to install your app.
To name a few I can think of Appaloosa Store, Apperian, MobileIron...
I hope this will help you!
Your best bet is a Google Play Private Channel.
Its basically creating a private channel for your domain, for which only people part of your domain could access the app. There's a setting in your google apps control panel, "Allow users to access Google Play Private Channel" which you would have to untick.
Then when deploying the app check "Make this application available only to users of my Google Apps domain".
Have a look at this link, it gives you an in depth guide how to go about publishing an app to a private channel.
http://www.techrepublic.com/blog/google-in-the-enterprise/deploy-private-android-apps-on-google-play/
Alternatively, you could provide a download link to the actual apk file on your website (once your consumer has paid for the product) and just give them instructions on how to install the it. eg. Enable "Unknown Sources" on Android Settings, then install the apk file.
I hope this helps.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 years ago.
Improve this question
Suppose I have a freshly compiled and tested 100 MB software. I want to eventually distribute it and sell it online as a product. This is a cross-platform product (done in C++).
What are the needed technical steps to achieve this? For each step, a description and an example of some software (if pertinent) would help. Also, how important is it would be helpful too.
My problem is that it is not really clear what are the stages to go through to release a software online. This list would help me a lot to know what steps I should investigate in priority.
What I am not talking about / interested in (because it is mainly the results I got while searching for this):
Website building;
Marketing & Sales;
Continuous Integration servers;
Steam, Mac Store, Windows Store;
Open Source.
Steps I identified:
Obfuscate: not sure about this one;
Licensing System: activation code system integrated in the software directly (See Digital River, SafeNet, Reprise, Flexera);
Installers: MSI for Windows (see Wix), DMG for mac;
Code Signing: ensures that your users do not get warnings (Verisign, GlobalSign...)
Free Trial Distribution: putting the installers on our own site is risky because of bandwidth and lags. Your users should be able to download a free trial quickly wherever they are. So a CDN would help (AWS CloudFront).
Auto Update System: notifiy the users, download and install new versions (Omaha);
Activation: this allows the user to activate the product online or directly from within the product;
I think that these two steps are the missing pieces in your list:
Write documentation (in your case PDF/RTF/HTML, or online tutorial)
Integrate a payment provider that will accept the payment on behalf of you
With the above two steps you should be ready to go.
There are some books that I can recommend you (they are 10 year old now, but you see shareware/try before you buy/ software is an old thing - nowadays people tend to write web apps or mobile mostly):
http://www.alibris.com/From-Program-to-Product-Turning-Your-Code-Into-a-Saleable-Product-Rocky-Smolin/book/10572213?matches=50
http://www.alibris.com/Micro-Isv-From-Vision-to-Reality-Bob-Walsh/book/9122742?matches=37
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
I am looking for an installer solution like it is used for Google Chrome:
When you click Download, you don't actually download the installer, but a very small Downloader, which then downloads the Chrome Installer, and launches it afterwards.
I know Sweet Labs is developing Ignite, but it is still in closed beta.
Are there any similar solutions out there, which are ready to use?
How about Google Omaha? (Actually used by Google Chrome) It seems to be the thing.
The Omaha project provides a shared autoupdate and install system for
Windows client products at Google that works on multiple Windows
platforms, including Windows Vista. Goals include the following:
One autoupdate mechanism which allows teams to roll out updates with no dependencies on other product teams, without having to write
their own client or server logic One autoupdate server that handles
all autoupdate requests - each product team will not need to roll out
and manage their own server One desktop autoupdate client shared by
all desktop client software - there will not be separate programs
running for each installed application
A tiny meta-installer which includes the update client (and knows how to install it if necessary) and a reference to the desired
application which the update client can then download and install
One-click web install of applications once the update client is installed
Support for rich update deploy logic allowing multiple tracks for public release, beta, development and "canary" experiments
Support for restricted user environments; for example, users without administrator privileges
Providing a shared runtime for other functionality common to all Google client applications: Crash reporting
Advanced Installer can do that too. It creates a small executable that can launch an MSI package from an URL you specify, so the package downloaded by the user is very small. As a bonus, you can split the application in features, and set it to create one CAB archive for each feature, so the actual install process will download only the CAB files for the features installed, reducing the download time for users that don't install all the features.
To have the user see only a small progress bar instead of full MSI dialogs you just need to tick a checkbox from Install Parameters page.
However, you should now that this feature is available only in the commercial licenses, you need at least a Professional license. You can test it, during the trial period access to all of its features is not restricted.
I now have this quite complete list of solutions:
Google Omaha
AdvancedInstaller
Somoto BetterInstaller ( + adds recommendations from which you make money)
Ignite (not available yet)
Or possibly create your own using the WiX Toolset, NSIS or Inno Setup.
All of those are free solutions, except for AdvancedInstaller. It has a free edition too, but cannot be used to create this package type; for this you need at least a Professional edition.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 5 years ago.
Improve this question
I have two separate iOS apps, one is a client and one is a server. They need to be used together, either by itself is useless. Clients are free, server has a cost to use.
I know I can submit this as a single app, and maybe have the server functionality be unlocked with an In App Purchase.
But what if I want to submit this as two separate apps? What is the procedure to submit two related apps for Apple review? I can set the release date for each of them to a date in the future in case one gets approved and the other is rejected and needs rehabilitation. That way I can coordinate a single launch date for both of them once both have been approved.
Anyone with experience they would be willing to share?
Here is an example of why I might want to do this: Let's say my server app is very large in size because it has content, graphics, whatever. The server is used at a large gathering and many people want to join the fun as clients. They all need to download the client app over cellular data at the venue at that time. I want the related client app to have a small footprint.
They need to be used together, either by itself is useless.
This is the reason why you should make a single app with the server functionality locked as an In App Purchase. Think about it again.
People who download a free client version cannot use it anyway without buying another app. Not good.
People who download a free client version cannot easily upgrade it to the full version. Not good.
People who go through the hassle and install both apps have to somehow switch between them. They have one icon more on their home screen too.
If you can, ship a single app. Tell your users what's going on in the first-launch information view, letting them upgrade instantly.
To get around the client server uselessness without the other, first submit a paid app that does both, then submit the free client, then submit the paid server, then, if sales and revenue trends so indicate this to be a revenue optimization, remove the combo app from sale.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I recently bought the new Plesk software and im unsure on how to re-brand the site to our company logos and themes.
Does anyone know the steps to changes these settings or a manual that would answer my questions?
Regards,
Oliver James
Well, it really depends on how much work you want to do. You can do as little as changing the logo--which is quite simple--to as much as completely retheming the interface to match your company's brand. The path of least resistance is to copy an existing skin and modify it to suit your needs.
Either way, start in the admin interface and go to the Server config page. The two options that should interest you are there: Logo Setup and Interface Management. Changing the logo is pretty obvious, so I'll stick to the Interface Management part.
Once in the Interface Management section, click on the Skins tab. The first thing you should do here is find the skin that most closely resembles what you'd like your finished product to look like. You'll notice on the list of skins that there's an icon of a floppy disk; clicking on this icon will allow you to download a .zip or .tar.gz file containing all the files for the skin.
Now you just need to alter the skin as necessary. I recommend setting up a development server (or a virtualized server) where you can play with Plesk without causing any damage to your production server. And, of course, best practices dictate that you should probably put it all under source control to make sure nothing goes wrong.
Anyhow, once you've made your changes and you're satisfied with the results, go back to the Skins page in the Interface Management section and click the Add New Skin button. Zip up your skin (to match the way it was zipped when you downloaded the base skin) and upload the file. Once you've uploaded it, you can then choose the skin from the Skins page. To be on the safe side, I recommend creating a dummy client user and testing out the skin on your production environment before switching any existing users to the new skin, just in case there's a problem with the skin.
And once you're satisfied that your newly-modified skin works on the production site, go ahead and switch all your existing users over.