baker icon indicating copy to clipboard operation
baker copied to clipboard

Do magazines created thru baker include an app?

Open ddtsonev opened this issue 12 years ago • 10 comments

Hello. Let me say that I'm not a developer and have almost zero knowledge in that area.

My question, after reading the tutorials in the baker website is: When a developer creates an issue of a magazine thru baker and submits it to Apple for newsstand, will all future be under one app, or every new one will be as a separate one.

Also, how will the app look like?

Thank you for your answers.

ddtsonev avatar Aug 31 '13 21:08 ddtsonev

Hi, you will need to submit one app for your magazine that is linked to a server where your issues are/will be stored, so the users may download them. Using MagRocket it is quite easy to manage those issues. Let me know if you have more questions.

You may configure the app looks in the Baker xcode project.

rebeloper avatar Aug 31 '13 22:08 rebeloper

One magazine = 1 app You submit your issues from a backend server.

So if you want to create two magazine, you will need two baker apps each submitted individually to the app store.

nicholasmartin avatar Sep 01 '13 05:09 nicholasmartin

Thanks very much for your answers, guys. More questions arise:

Is there a default look to the app, if you don't configure it and where can I check it out? I didn't quite get from your answers- after submitting the first magazine issue in an app to the app store, can we then submit our future issues to the same app?

Also, if our magazine is free, do we need to use magrocket?

Can we use baker for kindle as well?

ddtsonev avatar Sep 01 '13 07:09 ddtsonev

Baker Framework is the iOS magazine application. You need to open Baker in Xcode in order to edit a few things. Inside the BakerShelf/img folder you will find all the default artwork for the look of the shelf (the place where you see all the Magazines issues listed). Simply create your own images and replace the default baker images. There is also a few variables you can change in the BakerShelf/UIConstants.h file such as fonts and colors.

If you follow the standalone book guide (it's easier to setup) you can see how it looks (requires a mac with Xcode installed).

The Baker Framework is as mentioned the iOS app. The Baker app calls a server to see which issues are available, which means you need a server to place your magazine issues on. Think of the Baker app as a "shell" that pulls in issues from your server.

Once your Baker app has been submitted and approved, in order to add new issues you would simply upload your new issue to your server. Depending on your setup, you might need to manually edit your shelf.json file (which is the file that keeps track of all your issues and tells the Baker app what is available).

If all your issues are free, there is no need to use Magrocket, but Magrocket does make things a lot easier once setup. It is a backend management system where you can add new issues and then it will automatically update your shelf.json file. Correct me if I'm wrong guys, but even if your issues are free, I would recommend using a backend system like Magrocket to keep things simple in the long run.

If you are not comfortable with setting up your own server to host your magazines, you could take a quick look at http://MagBoy.co which is something I'm currently working on. You simply create a free account and then upload your magazines. I've also added about 20 short videos that show you how to get setup and especially customize and run the Baker iOS app in Xcode. I have customized the Baker app slightly, so that it's almost ready to go. You just need to add your app id from apple and add your subscription product id.

Baker is only for iOS. I know there are some people working on a build for Android, so no Kindle.

Anyways, sorry for the rant here and shameless plug, just wanted to clarify my answer on the one magazine = one app question, as that's one of the questions I also had when first starting out :)

nicholasmartin avatar Sep 01 '13 08:09 nicholasmartin

Thanks for the exhaustive answer, lifestylenetworker.

As we'll probably outsource this whole thing, how much do you think is a fare price for someone to do all these things, provided we'll give him the content for the magazine (the first issue can be as small as 30 pages, but we want it to include videos) and our apple developer account and he has to do the rest?

ddtsonev avatar Sep 01 '13 08:09 ddtsonev

Thanks, no need to apologize, your bring value to the community. Sp plug away!

lifestylenetworker mailto:[email protected] September 1, 2013 3:46 AM

Baker Framework is the iOS magazine application. You need to open Baker in Xcode in order to edit a few things. Inside the BakerShelf/img folder you will find all the default artwork for the look of the shelf (the place where you see all the Magazines issues listed. Simply create your own images and replace the default baker images. There is also a few variables you can change in the BakerShelf/UIConstants.h file such as fonts and colors.

If you follow the standalone book guide (it's easier to setup) you can see how it looks (requires a mac with Xcode installed).

The Baker Framework is as mentioned the iOS app. The Baker app calls a server to see which issues are available, which means you need a server to place your magazine issues on. Think of the Baker app as a "shell" that pulls in issues from your server.

Once your Baker app has been submitted and approved, in order to add new issues you would simply upload your new issue to your server. Depending on your setup, you might need to manually edit your shelf.json file (which is the file that keeps track of all your issues and tells the Baker app what is available).

If all your issues are free, there is no /need/ to use Magrocket, but Magrocket does make things a lot easier once setup. It is a backend management system where you can add new issues and then it will automatically update your shelf.json file. Correct me if I'm wrong guys, but even if your issues are free, I would recommend using a backend system like Magrocket to keep things simple in the long run.

If you are not comfortable with setting up your own server to host your magazines, you could take a quick look at http://MagBoy.co which is something I'm currently working on. You simply create a free account and then upload your magazines. I've also added about 20 short videos that show you how to get setup and especially customize and run the Baker iOS app in Xcode. I have customized the Baker app slightly, so that it's almost ready to go. You just need to add your app id from apple and add your subscription product id.

Baker is only for iOS. I know there are some people working on a fork for Android, so no Kindle.

Anyways, sorry for the rant here and shameless plug, just wanted to clarify my answer on the one magazine = one app question, as that's one of the questions I also had when first starting out :)

— Reply to this email directly or view it on GitHub https://github.com/Simbul/baker/issues/1105#issuecomment-23621101.

ddtsonev mailto:[email protected] August 31, 2013 4:06 PM

Hello. Let me say that I'm not a developer and have almost zero knowledge in that area.

My question, after reading the tutorials in the baker website is: When a developer creates an issue of a magazine thru baker and submits it to Apple for newsstand, will all future be under one app, or every new one will be as a separate one.

Also, how will the app look like?

Thank you for your answers.

— Reply to this email directly or view it on GitHub https://github.com/Simbul/baker/issues/1105.

Appmantx avatar Sep 01 '13 14:09 Appmantx

With Magboy, Are we still going to need to install Magrocket?

lifestylenetworker mailto:[email protected] September 1, 2013 3:46 AM

Baker Framework is the iOS magazine application. You need to open Baker in Xcode in order to edit a few things. Inside the BakerShelf/img folder you will find all the default artwork for the look of the shelf (the place where you see all the Magazines issues listed. Simply create your own images and replace the default baker images. There is also a few variables you can change in the BakerShelf/UIConstants.h file such as fonts and colors.

If you follow the standalone book guide (it's easier to setup) you can see how it looks (requires a mac with Xcode installed).

The Baker Framework is as mentioned the iOS app. The Baker app calls a server to see which issues are available, which means you need a server to place your magazine issues on. Think of the Baker app as a "shell" that pulls in issues from your server.

Once your Baker app has been submitted and approved, in order to add new issues you would simply upload your new issue to your server. Depending on your setup, you might need to manually edit your shelf.json file (which is the file that keeps track of all your issues and tells the Baker app what is available).

If all your issues are free, there is no /need/ to use Magrocket, but Magrocket does make things a lot easier once setup. It is a backend management system where you can add new issues and then it will automatically update your shelf.json file. Correct me if I'm wrong guys, but even if your issues are free, I would recommend using a backend system like Magrocket to keep things simple in the long run.

If you are not comfortable with setting up your own server to host your magazines, you could take a quick look at http://MagBoy.co which is something I'm currently working on. You simply create a free account and then upload your magazines. I've also added about 20 short videos that show you how to get setup and especially customize and run the Baker iOS app in Xcode. I have customized the Baker app slightly, so that it's almost ready to go. You just need to add your app id from apple and add your subscription product id.

Baker is only for iOS. I know there are some people working on a fork for Android, so no Kindle.

Anyways, sorry for the rant here and shameless plug, just wanted to clarify my answer on the one magazine = one app question, as that's one of the questions I also had when first starting out :)

— Reply to this email directly or view it on GitHub https://github.com/Simbul/baker/issues/1105#issuecomment-23621101.

ddtsonev mailto:[email protected] August 31, 2013 4:06 PM

Hello. Let me say that I'm not a developer and have almost zero knowledge in that area.

My question, after reading the tutorials in the baker website is: When a developer creates an issue of a magazine thru baker and submits it to Apple for newsstand, will all future be under one app, or every new one will be as a separate one.

Also, how will the app look like?

Thank you for your answers.

— Reply to this email directly or view it on GitHub https://github.com/Simbul/baker/issues/1105.

Appmantx avatar Sep 01 '13 14:09 Appmantx

It's a competing product...


From: Appmantx [email protected] To: Simbul/baker [email protected] Sent: Sunday, September 1, 2013 9:38 AM Subject: Re: [baker] Do magazines created thru baker include an app? (#1105)

With Magboy, Are we still going to need to install Magrocket?

lifestylenetworker mailto:[email protected] September 1, 2013 3:46 AM

Baker Framework is the iOS magazine application. You need to open Baker in Xcode in order to edit a few things. Inside the BakerShelf/img folder you will find all the default artwork for the look of the shelf (the place where you see all the Magazines issues listed. Simply create your own images and replace the default baker images. There is also a few variables you can change in the BakerShelf/UIConstants.h file such as fonts and colors.

If you follow the standalone book guide (it's easier to setup) you can see how it looks (requires a mac with Xcode installed).

The Baker Framework is as mentioned the iOS app. The Baker app calls a server to see which issues are available, which means you need a server to place your magazine issues on. Think of the Baker app as a "shell" that pulls in issues from your server.

Once your Baker app has been submitted and approved, in order to add new issues you would simply upload your new issue to your server. Depending on your setup, you might need to manually edit your shelf.json file (which is the file that keeps track of all your issues and tells the Baker app what is available).

If all your issues are free, there is no /need/ to use Magrocket, but Magrocket does make things a lot easier once setup. It is a backend management system where you can add new issues and then it will automatically update your shelf.json file. Correct me if I'm wrong guys, but even if your issues are free, I would recommend using a backend system like Magrocket to keep things simple in the long run.

If you are not comfortable with setting up your own server to host your magazines, you could take a quick look at http://MagBoy.co which is something I'm currently working on. You simply create a free account and then upload your magazines. I've also added about 20 short videos that show you how to get setup and especially customize and run the Baker iOS app in Xcode. I have customized the Baker app slightly, so that it's almost ready to go. You just need to add your app id from apple and add your subscription product id.

Baker is only for iOS. I know there are some people working on a fork for Android, so no Kindle.

Anyways, sorry for the rant here and shameless plug, just wanted to clarify my answer on the one magazine = one app question, as that's one of the questions I also had when first starting out :)

— Reply to this email directly or view it on GitHub https://github.com/Simbul/baker/issues/1105#issuecomment-23621101.

ddtsonev mailto:[email protected] August 31, 2013 4:06 PM

Hello. Let me say that I'm not a developer and have almost zero knowledge in that area.

My question, after reading the tutorials in the baker website is: When a developer creates an issue of a magazine thru baker and submits it to Apple for newsstand, will all future be under one app, or every new one will be as a separate one.

Also, how will the app look like?

Thank you for your answers.

— Reply to this email directly or view it on GitHub https://github.com/Simbul/baker/issues/1105.

— Reply to this email directly or view it on GitHub.

nin9creative avatar Sep 01 '13 14:09 nin9creative

Like Andrew mentioned, these are two different solutions to a backend server.

nicholasmartin avatar Sep 01 '13 14:09 nicholasmartin

@lifestylenetworker I'm interested in the pricing once you're over the beta.

rebeloper avatar Sep 01 '13 16:09 rebeloper