Category Archives: iOS

Sending iOS Push Notifications using Python module PyAPNS

September 21, 2014 Denis Kutlubaev Leave a comment

I have written a small module, that sends a push notification using PyAPNS.

This is how my sender.py module looks like:

# -*- coding: utf-8 -*-
from django.db import connection
from apns import APNs, Frame, Payload


class Sender:
	def send(self):
		apns = APNs(use_sandbox=True, cert_file='Cert.pem', key_file='Key.pem')
		token_hex = 'e4d4e96ec8ac3dd003e0129347b3421fe53ba49811b3803c4e99cfdc60293c94'
		message = "Hello"
		payload = Payload(alert=message.decode('utf-8'), sound="default", badge=0)
		apns.gateway_server.send_notification(token_hex, payload)

# -*- coding: utf-8 -*-

from django.db import connection

from apns import APNs, Frame, Payload

class Sender:

def send(self):

apns = APNs(use_sandbox=True, cert_file='Cert.pem', key_file='Key.pem')

token_hex = 'e4d4e96ec8ac3dd003e0129347b3421fe53ba49811b3803c4e99cfdc60293c94'

message = "Hello"

payload = Payload(alert=message.decode('utf-8'), sound="default", badge=0)

apns.gateway_server.send_notification(token_hex, payload)

Here is a Sender class inside sender.py module. It has one method send. Inside this method I create an object of APNs class, create a payload and send it using this object.
Cert.pem and Key.pem files are inside the folder with this module. They can be created using this tutorial. Also that folder contains apns.py module file with PyAPNS code.

To send a sample push notification from a command line I use following commands. First, I enter the folder with module. It is called notification_sender:

$ cd ~/Documents/common-app-server/app_server/notification_sender

1	$ cd ~/Documents/common-app-server/app_server/notification_sender

Or on server:

# cd ~/www/den.ladby.ru/public/common-app-server/app_server/notification_sender

1	# cd ~/www/den.ladby.ru/public/common-app-server/app_server/notification_sender

Then I enter to the python console:

$ python

$ python

Then I import Sender class from sender module:

from sender import Sender

1	from sender import Sender

Create a sender object of a Sender class:

sender = Sender()

1	sender = Sender()

And finally send a notification:

sender.send()

1	sender.send()

All you need to do to finish the job is to enter a PEM pass phrase:

Enter PEM pass phrase:

1	Enter PEM pass phrase:

Currently, the device token is hardcoded, I am planning to use SQLite entries with collected tokens. I use Django to collect tokens.

I would like to add that if you change somehow the source file of a module, you should reenter python console and recreate object to make changes work.

iOS

Краткое введение в push-уведомления на iOS

September 19, 2014 Denis Kutlubaev 2 Comments

Иногда нужно сообщить пользователю мобильного приложения о каком-то интересном событии. Таким событием может быть появление нового сообщения для пользователя. При этом, если приложение будет постоянно висеть в фоне и проверять периодически сервер, то это будет крайне неэкономно с точки зрения заряда батареи. Поэтому и придумали push – уведомления. Это сообщения от сервера, которые приходят на телефон пользователя, даже когда приложение не запущено. Отправлять их должен ваш сервер, но не напрямую на телефоны всех пользователей, а через специальные сервера Apple, которые называются APNS – Apple Push Notification Servers. Работают они так:

Что нужно, чтобы отправить push – уведомление с сервера на APNS?

Сертификат и ключ к сертификату для данного приложения. iOS-разработчик может их предоставить. См. туториал ниже по их генерации.
Токен устройства. Это хеш-код, который идентифицирует данное устройство в связке с приложением на APNS. Токены нужно собирать в отдельную таблицу на вашем сервере. Для этого необходимо разработать API запрос, по которому iOS-разработчик сможет отправлять на сервер связку токен устройства – имя пользователя или просто токен устройства. Токен может отправляться на ваш сервер при каждом запуске приложения. При получении на сервере соответствующую запись нужно обновлять.
JSON с описанием уведомления. Зная токен для данного пользователя и имея сертификат, можно сформировать JSON специального вида, содержащий текст уведомления и отправить его по SSL на APNS. APNS дальше уже отсылает уведомление на телефон. Имея токены, можно разрабатывать и отправлять с сервера любые push – уведомления, которые потребуются. Для Python уже есть готовые библиотеки для отправки push – уведомлений. Я полагаю, что для PHP, они наверняка тоже есть, так что тут лучше с нуля код полностью не писать и не тратить силы.

JSON может иметь разную конфигурацию в зависимости от ваших потребностей. Полное описание смотрите в документации. Ссылка ниже.

Пример JSON:

{
	"aps":
	{
		"alert": "Hello, world!",
		"sound": "default"
	}
}

{

"aps":

{

"alert": "Hello, world!",

"sound": "default"

}

Другой вариант:

{
	"aps":
	{
		"alert":
		{
			"action-loc-key": "Open",
			"body": "Hello, world!"
		},
		"badge": 2
	}
}

{

"aps":

{

"alert":

{

"action-loc-key": "Open",

"body": "Hello, world!"

"badge": 2

}

Здесь badge – это номер, который появится на иконке приложения после прихода уведомления. Он может быть равен например числу новых сообщения для пользователя.
body – текст уведомления

Подробнее:

Apple Push Notification Service

Tutorial

Написал ТЗ для нашего серверного разработчика на работе и решил перенести часть его сюда, так как ТЗ большей частью представляет из себя популярное изложение того, что такое push-уведомления и как их создавать на сервере.

Немаловажный аспект: push-уведомления являются бесплатным сервисом от Apple, то есть за эксплуатацию APNS платить не надо. Вся стоимость их поддержки – это стоимость поддержки вашего сервера. Но даже так, они могут оказаться дорогим удовольствием, особенно если вы платите за мощности в облаке. Также стоит еще раз сказать, что для отправки push-уведомлений необходим SSL, который не все облачные сервисы предоставляют бесплатно.

Android, iOS, Web Development

Searching for the best technology for a mobile app backend development

September 3, 2014 Denis Kutlubaev Leave a comment

Client-server applications with a mobile app client are more interesting than mobile standalone applications. They offer a new type of features for users like daily updated content. That is why at some moment of my mobile developer career I decided to learn how to create a server side for my mobile applications myself. As it happens usually in IT, there were a lot of techologies and programming languages, that I could start to learn and use for achieve my goals. Of course, if I would stop on the first one, that I have tried, I would lose, because one can never find the best way without understanding what other ways give and without any broad enough knowledge. I think, it is a good idea to get familiar with minuses of each technology before starting to learn and use it.

This is my story. I started with Java Servlets and I have tried also PHP and Python at the moment. Also I have read about Ruby On Rails and Node.JS. Finally, I stopped currently at using Python with Django.

Between Java Servlets and Python I choose Python. Development on Python it is much faster than on Java Servlets. It has no complex and sensible configuration files. Python offers iterative development, you can just refresh a web page and see results instantly. With Java Servlets you have to wait some time every time you update something. Python is like scripting language, despite it is compiled to some kind of byte code. I also liked python for it’s clean syntax, despite I am friendly with Java too. Using HTML templates with Python is easier to me, than creating JSP pages with servlets. Just for information, I use Sublime Text 2 as a Python editor with a Lazy color theme. It is really convenient editor.

I will not try PHP, because it is not valuable now, loses it’s popularity. It looks like Python offers almost the same features but even is better because of syntax, because it is compiled and because it offers full OOP support from the start and you can create all kind of applications including desktop applications with it. Also there are a lot of scientific and data analysis libraries on Python, that can be useful to create sophisticated back-end.

I don’t like the idea of using generally considered to be slow Javascript at the backend in Node.js. Also Node.js needs it’s own HTTP server.

What about Parse, QuickBlox and other ready for use backend services? I don’t want to use them, because I want to be able to create my own-backends with complete understanding of their code and work. These are good to create something easy and usual, but not something unique.

Probably I will try also Ruby on Rails at some moment.

But currently I am completely satisfied with Python. I want to get familiar with Django framework on Python too.

There are also open-source backends like Baasbox: http://www.baasbox.com/. But I haven’t tried it yet. Looks like it is written on Java, because needs JVM.

The best way to create Forms in iOS

July 30, 2014 Denis Kutlubaev Leave a comment

I think the best way to create forms in iOS is by using FXForms open-source project. It can be found in Github. There are some alternatives, but only FXForms support iOS 6. However, FXForms is still not flexible enough. So, if you want to create something completely custom by design, probably, it will not be a suitable solution.

The main advantage of this approach is that your forms become very compact. Also you will save tons of time and your nerves creating many similar and boring forms after you understand how to use FXForms. But not so easy. The main difficulty is to learn how to declare fields.

There are many examples in the project repository. This is not a tutorial, but rather an introduction. Basically what you do is you inherit from FXFormViewController to create a form view controller.

#import "RRBaseTableViewController.h"
#import "FXForms.h"

@interface RRBaseAddResumeViewController : FXFormViewController

#import "RRBaseTableViewController.h"

#import "FXForms.h"

@interface RRBaseAddResumeViewController : FXFormViewController

And you create a form object inheriting NSObject, that conforms to FXForm protocol.

Header file:

#import <Foundation/Foundation.h>
#import <FXForms.h>

typedef NS_ENUM(NSInteger, Gender)
{
  GenderMale = 0,
  GenderFemale
};


@interface RRCreateResumeForm : NSObject <FXForm>

@property (nonatomic, copy) NSString *surname;
@property (nonatomic, copy) NSString *name;
@property (nonatomic, copy) NSDate *birthday;
@property (nonatomic, assign) Gender gender;

@end

#import <Foundation/Foundation.h>

#import <FXForms.h>

typedef NS_ENUM(NSInteger, Gender)

{

GenderMale = 0,

GenderFemale

};

@interface RRCreateResumeForm : NSObject <FXForm>

@property (nonatomic, copy) NSString *surname;

@property (nonatomic, copy) NSString *name;

@property (nonatomic, copy) NSDate *birthday;

@property (nonatomic, assign) Gender gender;

@end

Implementation file:

#import "RRCreateResumeForm.h"

@implementation RRCreateResumeForm


- (NSArray *)fields
{
  return @[
           @{FXFormFieldKey: @"surname", FXFormFieldTitle: @"Фамилия"},
           @{FXFormFieldKey: @"name", FXFormFieldTitle: @"Имя"},
           @{FXFormFieldKey: @"birthday", FXFormFieldTitle: @"Дата рождения"},
           @{FXFormFieldKey: @"gender", FXFormFieldOptions: @[@"Мужской", @"Женский"], FXFormFieldTitle: @"Пол"}
           ];
}

@end

#import "RRCreateResumeForm.h"

@implementation RRCreateResumeForm

- (NSArray *)fields

{

return @[

@{FXFormFieldKey: @"surname", FXFormFieldTitle: @"Фамилия"},

@{FXFormFieldKey: @"name", FXFormFieldTitle: @"Имя"},

@{FXFormFieldKey: @"birthday", FXFormFieldTitle: @"Дата рождения"},

@{FXFormFieldKey: @"gender", FXFormFieldOptions: @[@"Мужской", @"Женский"], FXFormFieldTitle: @"Пол"}

];

}

@end

And this is how you stick FormViewController with it’s Form:

- (void)createResumeClicked:(id)sender
{
  RRCreateResumeViewController *createResumeViewController = [[RRCreateResumeViewController alloc] init];
  RRCreateResumeForm *form = [[RRCreateResumeForm alloc] init];
  createResumeViewController.formController.form = form;
  
  [self.navigationController pushViewController:createResumeViewController animated:YES];
}

- (void)createResumeClicked:(id)sender

{

RRCreateResumeViewController *createResumeViewController = [[RRCreateResumeViewController alloc] init];

RRCreateResumeForm *form = [[RRCreateResumeForm alloc] init];

createResumeViewController.formController.form = form;

[self.navigationController pushViewController:createResumeViewController animated:YES];

}

iOS

iOS State Restoration vs NSCoding

July 29, 2014 Denis Kutlubaev Leave a comment

My goal was to create a mechanism to store user interface state in my app. So I decided to study Apple’s State Preservation and Restoration, that was first introduced in iOS 6. As far, as I could understand on my own experience use:
1. iOS State Preservation and Restoration, if you want to store navigation state in an app, that doesn’t change root controller of a window at some moment. It is convenient in this case.
2. NSCoding Protocol for simpler tasks, when you don’t want to navigate, but want to save interface states for only several forms, because it is much more flexible – you completely control the process.

I have tried to implement State Preservation and Restoration that was introduced in iOS 6 in my app but unfortunately I failed. The problem was that it’s mechanism is not flexible enough. It can restore state of View Controllers in a linear tree. But if your app as mine changes a Root Controller of your Window at some moment after user logins, for instance, this mechanism will not work. However, in other apps with simpler architecture it can be successfully used. It helps to bring a user right to the place where he stopped using your app last time even if app is removed from the background.

There is a good presentation on this topic on SlideShare.

I used this tutorial also. There is a code on GitHub, that works.

However, there is a good flexible alternative: saving objects to text files using NSCoding protocol:

- (void)viewDidLoad
{
  [super viewDidLoad];

  // Restoring form object from the file
  NSString *formFilePath = [self formFilePath];
  RRCreateResumeForm *form = [NSKeyedUnarchiver unarchiveObjectWithFile:formFilePath];
  if (form != nil) {
    self.formController.form = form;
  }
}


- (void)viewWillDisappear:(BOOL)animated
{
  [super viewWillDisappear:animated];
  
  // Saving the form object to the file
  NSString *formFilePath = [self formFilePath];
  [NSKeyedArchiver archiveRootObject:self.formController.form toFile:formFilePath];
}


// Returns a file path to the file with stored form data for form controller
- (NSString *)formFilePath
{
  NSArray *paths = NSSearchPathForDirectoriesInDomains(NSDocumentDirectory, NSUserDomainMask, YES);
  NSString *documentsDirectory = [paths objectAtIndex:0];
  NSString *formClassName = NSStringFromClass( [self.formController.form class] );
  NSString *formFileName = [NSString stringWithFormat:@"%@.txt", formClassName];
  NSString *formFilePath = [documentsDirectory stringByAppendingPathComponent:formFileName];
  
  return formFilePath;
}

- (void)viewDidLoad

{

[super viewDidLoad];

// Restoring form object from the file

NSString *formFilePath = [self formFilePath];

RRCreateResumeForm *form = [NSKeyedUnarchiver unarchiveObjectWithFile:formFilePath];

if (form != nil) {

self.formController.form = form;

}

- (void)viewWillDisappear:(BOOL)animated

{

[super viewWillDisappear:animated];

// Saving the form object to the file

NSString *formFilePath = [self formFilePath];

[NSKeyedArchiver archiveRootObject:self.formController.form toFile:formFilePath];

}

// Returns a file path to the file with stored form data for form controller

- (NSString *)formFilePath

{

NSArray *paths = NSSearchPathForDirectoriesInDomains(NSDocumentDirectory, NSUserDomainMask, YES);

NSString *documentsDirectory = [paths objectAtIndex:0];

NSString *formClassName = NSStringFromClass( [self.formController.form class] );

NSString *formFileName = [NSString stringWithFormat:@"%@.txt", formClassName];

NSString *formFilePath = [documentsDirectory stringByAppendingPathComponent:formFileName];

return formFilePath;

}

Android, iOS

Open-Source Android and iOS Projects

June 18, 2014 Denis Kutlubaev Leave a comment

I highly recommend you to look at popular open-source projects in your field even before you start developing something. Because almost everything you want to create is already created by the community with a very high quality. I understood this a year ago when I discovered Open source in iOS for myself and now I discovered it in Android. In this post I will give you a MUST look list of references and projects.

A list of important and popular open-source projects on GitHub for Android and iOS can be found here:

By best match:

By most stars:

By most forks:

Android, iOS

StackOverflow Highest Voted Android and iOS Questions

June 10, 2014 Denis Kutlubaev Leave a comment

Android

iOS

How to use a new model of CocoaPods PodSpec updates

June 5, 2014 Denis Kutlubaev Leave a comment

Recently CocoaPods started to use web service to load new PodSpecs.

I will skip a moment, where you need to register your projects to yourself. Basicly, guys that manage CocoaPods have created a web service, that knows, which computer has permissions to which Pod.

But when you have done this, you have to know, how to publish new versions of your Pods. You have to create a tag and push it on a new version as before and use that tag in your pod spec file.

$ git tag -a 1.0.2 -m '1.0.2'
$ git push --tags

1 2	$ git tag -a 1.0.2 -m '1.0.2' $ git push --tags

Then you should check your new updated pod spec.

pod spec lint

1	pod spec lint

Then you just push your pod spec to a web service. Now you do not have to create one more folder for a new PodSpec file, copy it to your Specs fork and create a pull request. Everything is much simpler!

$ pod trunk push ./DKProgressHUD.podspec

1	$ pod trunk push ./DKProgressHUD.podspec

Here it is important to tell a path to your pod spec file. I use here a dot since my pod spec file is located in the folder, where I am currently in Terminal.
For more information read a blog of CocoaPods project.

If you are asked to register a session first, do this:

$ pod trunk register name@example.org 'Your Name' --description='macbook pro'

1	$ pod trunk register name@example.org 'Your Name' --description='macbook pro'

In my case:

$ pod trunk register alwawee@gmail.com 'Dennis Kutlubaev' --description='iMac at the office'

1	$ pod trunk register alwawee@gmail.com 'Dennis Kutlubaev' --description='iMac at the office'

iOS

New cool custom Activity Indicator for iOS

May 26, 2014 Denis Kutlubaev Leave a comment

Recently I have created a new open-source project of an activity indicator for iOS, called DKProgressHUD.

Today I merged a contribution from Edan Lichtenstein, which significantly improves it. This is how it looks now on iPhone:

DKProgressHUD on GitHub

Available via Cocoapods:

pod DKProgressHUD

1	pod DKProgressHUD

Android, iOS

Mobile App Release Roadmap / Checklist

May 16, 2014 Denis Kutlubaev Leave a comment

Mobile App Release Checklist

1. Install new version above the old one.

2. Install your app to different devices, as many as you can (iPad, iPhone, iPhone 5, iPhone 3GS, Galaxy S4, Google Nexus 5, Nexus 3, very small screen size Android devices, etc.) Particularly, for Android and for iPad.

3. Check different geo locations, for example, Moscow, St. Petersburg, Ufa, etc., not the only one, where you live and develop the app.

4. Check that your app doesn’t load data to Documents folder, that is backed up in iCloud. All files should be marked as not backed up, if they can be downloaded again.

5. Check that your app doesn’t have iPad or iPhone words in the name.

6. Check, how data absence is handled when your app fails to load data from server. Particularly, on Android.

7. Check, how bad answers are handled, like HTML instead of JSON. Particularly, on Android.

8. Check, how bad objects in JSON are handled (like null objects or strings instead of objects, etc.). Particularly, on Android.

9. If you use In-App Purchases, check that they are activated for a new version in iTunes Connect.

10. If you use In-App Purchases, check that your app has in-apps if they are activated.

11. Check, how absence of internet is handled.

12. Check, how different operations with arrays and dictionaries are handled.

I am tired of being unsuccessful while releasing new versions of the apps to the AppStore and created a checklist. Always, I forget something to check, when I release an update. Hope, this will save your time, when you publish your app versions. Using the help of testers doesn’t improve final results in these cases, so you have to check all this shit yourself.

All these reasons in my developer experience created some shit in my life. And all these points have their own graves of my time. Check them all, when you decide to release your app version.

Alwawee

Category Archives: iOS

Sending iOS Push Notifications using Python module PyAPNS

Краткое введение в push-уведомления на iOS

Searching for the best technology for a mobile app backend development

The best way to create Forms in iOS

iOS State Restoration vs NSCoding

Open-Source Android and iOS Projects

StackOverflow Highest Voted Android and iOS Questions

How to use a new model of CocoaPods PodSpec updates

New cool custom Activity Indicator for iOS

Mobile App Release Roadmap / Checklist

iOS Development